#Dagger runs increase in duration, until machine is rebooted.

1 messages · Page 1 of 1 (latest)

drowsy stag
#

With a little over a months' worth of experience with Dagger, I've noticed that my run times seem to increase the longer I go between computer reboots.

I realized that my runs where slow, but it wasn't until a co-worker downloaded my repo to help me debug something that I realized that my machine was so slow compared to his (I was up to 16 min and his was < 2 min).

I rebooted my machine and my times decreased to match his, but I do notice that they slowly creep up and I fix by rebooting.

Should I look at my code or is it my infrastructure setup that maybe has a memory leak somewhere and is causing this?

My setup is:

  • OS Name Microsoft Windows 10 Enterprise
  • Version 10.0.19045 Build 19045
  • WSL v2
  • Ubuntu 20.04.6 LTS
  • Docker Desktop 4.24.2 (124339)
zinc wigeon
#

@drowsy stag do you have you runs connected to Dagger Cloud?

#

it'd be nice to see what's taking more time particularly

#

this is the first time that I've heard about this issue so my instinct tells me it might be something probably related to your project / setup

drowsy stag
#

No, everything is local.

My test project is a simple dotnet MVC application where I'm using the mcr.microsoft.com/dotnet/sdk:7.0 image to do the build step. Then I move to my next step which is code scanning where I use ubuntu:latest and update the packages and install curl. Then install snyk cli and run code scanning.

It's definitely not anything crazy.

Are there any commands you want me to run to save some timings or outputs?

zinc wigeon
drowsy stag
zinc wigeon
#

@drowsy stag maybe it's faster if we can jump into a quick #911305510882513037 session so you can show me what's up?

drowsy stag
#

@zinc wigeon , Sorry for the delay in my response. I was in training all last week. I picked this back up today and started with an experiment. I just did ten runs this morning and all the timings were relatively close to each other.

After this test, I would conclude that there is not a problem.

One difference between the code running now and the code I was previously running, where the timings were increasing after each run, is that my code now is the "fixed" version that came out of my other thread (https://discord.com/channels/707636530424053791/1030538312508776540/threads/1164601115795529808). It is very possible that the combination of things I was doing before the fix is what lead the problem and not anything related to Dagger.io.

Discord
Discord - A New Way to Chat with Friends & Communities

Discord is the easiest way to communicate over voice, video, and text. Chat, hang out, and stay close with your friends and communities.

zinc wigeon