« previous next »
Pages: 1 2 [All] |   Go Down

Author Topic: Significant commandline lag  (Read 5258 times)

0 Members and 1 Guest are viewing this topic.

alanjt

  • Needs a day job
  • Posts: 5352
  • Standby for witty remark...
Significant commandline lag
« on: February 18, 2015, 08:58:17 AM »
Running Civil 3D 2013.
I've noticed that, after a while of working in a file, running various lisp routines, etc., thing will get a bit laggy. Selection seems slower, etc. If I close the commandline, everything works fine. It's almost as if I'm allowed a certain number of executed lisp routines, then the commandline slows everything down. At this point, I close the commandline, hit f2, and go back to work, slightly annoyed.

Has anyone had any experience with this?
Logged
Civil 3D 2019 ~ Windohz 7 64bit
Dropbox

mjfarrell

  • Seagull
  • Posts: 14444
  • Every Student their own Lesson
Re: Significant commandline lag
« Reply #1 on: February 18, 2015, 01:33:57 PM »
it's just time dialation ...you are working at or near the speed of light

slow down a little and everything will return to normal
Logged
Be your Best


Michael Farrell
http://primeservicesglobal.com/

alanjt

  • Needs a day job
  • Posts: 5352
  • Standby for witty remark...
Re: Significant commandline lag
« Reply #2 on: February 18, 2015, 02:32:34 PM »
Quote from: mjfarrell on February 18, 2015, 01:33:57 PM
it's just time dialation ...you are working at or near the speed of light

slow down a little and everything will return to normal
I'm slightly depressed at how, aside from closing the commandline, that's actually the best solution.

I know this stems from the commandline being completely reconfigured. I never noticed this with 2012 or older.
Logged
Civil 3D 2019 ~ Windohz 7 64bit
Dropbox

mjfarrell

  • Seagull
  • Posts: 14444
  • Every Student their own Lesson
Re: Significant commandline lag
« Reply #3 on: February 18, 2015, 04:42:44 PM »
have to ask what OS are you running, and how much ram and is your page file 'fixed' or windows managed?
Logged
Be your Best


Michael Farrell
http://primeservicesglobal.com/

alanjt

  • Needs a day job
  • Posts: 5352
  • Standby for witty remark...
Re: Significant commandline lag
« Reply #4 on: February 18, 2015, 04:52:18 PM »
Quote from: mjfarrell on February 18, 2015, 04:42:44 PM
have to ask what OS are you running, and how much ram and is your page file 'fixed' or windows managed?
Windows 7
16GB
I don't understand the third question.
Logged
Civil 3D 2019 ~ Windohz 7 64bit
Dropbox

mjfarrell

  • Seagull
  • Posts: 14444
  • Every Student their own Lesson
Re: Significant commandline lag
« Reply #5 on: February 18, 2015, 05:00:07 PM »
see attached....

wonder if you have some form of memory leak?

check task manager/performance monitor to see where your memory is being allocated and to what processes
Logged
Be your Best


Michael Farrell
http://primeservicesglobal.com/

Rob...

  • King Gator
  • Posts: 3824
  • Take a little time to stop and smell the roses.
Re: Significant commandline lag
« Reply #6 on: February 19, 2015, 07:40:32 AM »
Just a stab in the dark here:
Does it make a difference if it is docked or not?
Logged
CAD Tech

lamarn

  • Swamp Rat
  • Posts: 636
Re: Significant commandline lag
« Reply #7 on: February 19, 2015, 08:21:07 AM »
Same here, it seems Autocad is becoming slower and slower with every new release..
We have a issue with netwerk speed and Autocad commands..
Logged
Design is something you should do with both hands. My 2d hand , my 3d hand ..

Rob...

  • King Gator
  • Posts: 3824
  • Take a little time to stop and smell the roses.
Re: Significant commandline lag
« Reply #8 on: February 19, 2015, 08:27:37 AM »
Quote from: lammerts on February 19, 2015, 08:21:07 AM
Same here, it seems Autocad is becoming slower and slower with every new release..
We have a issue with netwerk speed and Autocad commands..

I think that is a different issue from the OP. Yours is probably due to hardware. Newer versions will tend to be slower on borderline spec hardware or the info center is eating up bandwidth.
Logged
CAD Tech

Matt__W

  • Seagull
  • Posts: 12955
  • I like my water diluted.
Re: Significant commandline lag
« Reply #9 on: February 19, 2015, 08:52:23 AM »
I've heard issues with dual monitors and windows being docked on the primary vs. secondary makes a difference sometimes.

Still don't understand that one...  :|
Logged
Autodesk Expert Elite
Revit Subject Matter Expert (SME)
Owner/FAA sUAS Pilot @ http://skyviz.io

dgorsman

  • Water Moccasin
  • Posts: 2437
Re: Significant commandline lag
« Reply #10 on: February 19, 2015, 10:19:54 AM »
Primary vs. secondary monitor has to do with hardware acceleration - unless the desktop was "spanned" across both monitors there was no hardware acceleration on the second monitor.  Likely the same thing if the command line (as a separate palette) is undocked and on the second monitor.  That applied under XP, not certain if it still applies with more recent OS/DirectX/hardware combinations.
Logged
If you are going to fly by the seat of your pants, expect friction burns.

try {GreatPower;}
   catch (notResponsible)
      {NextTime(PlanAhead);}
   finally
      {MasterBasics;}

alanjt

  • Needs a day job
  • Posts: 5352
  • Standby for witty remark...
Re: Significant commandline lag
« Reply #11 on: February 19, 2015, 12:05:16 PM »
Quote from: mjfarrell on February 18, 2015, 05:00:07 PM
see attached....

wonder if you have some form of memory leak?

check task manager/performance monitor to see where your memory is being allocated and to what processes
acad, outlook, chrome (can be a memory hog), dropbox, nothing really out of the norm.

Quote from: RobDraw on February 19, 2015, 07:40:32 AM
Just a stab in the dark here:
Does it make a difference if it is docked or not?
It does not. I tried that since that was supposed to be a solution for lag with the properties palette (which I have to keep closed), but it made no difference.

Quote from: dgorsman on February 19, 2015, 10:19:54 AM
Primary vs. secondary monitor has to do with hardware acceleration - unless the desktop was "spanned" across both monitors there was no hardware acceleration on the second monitor.  Likely the same thing if the command line (as a separate palette) is undocked and on the second monitor.  That applied under XP, not certain if it still applies with more recent OS/DirectX/hardware combinations.
acad shows up in main display window and commandline is docked.
Logged
Civil 3D 2019 ~ Windohz 7 64bit
Dropbox

dgorsman

  • Water Moccasin
  • Posts: 2437
Re: Significant commandline lag
« Reply #12 on: February 19, 2015, 02:07:17 PM »
Not a solution but out of curiosity, does the lag start around the time the command line history hits the maximum lines it stores?

Is this strictly with running LISP routines, or is it commands and operations in general?  If the former, there could be some leftover references (previous settings, temporary lists, etc.) which aren't cleaned up properly.
Logged
If you are going to fly by the seat of your pants, expect friction burns.

try {GreatPower;}
   catch (notResponsible)
      {NextTime(PlanAhead);}
   finally
      {MasterBasics;}

alanjt

  • Needs a day job
  • Posts: 5352
  • Standby for witty remark...
Re: Significant commandline lag
« Reply #13 on: February 19, 2015, 03:01:32 PM »
Quote from: dgorsman on February 19, 2015, 02:07:17 PM
Not a solution but out of curiosity, does the lag start around the time the command line history hits the maximum lines it stores?
That's an interesting thought.

Quote from: dgorsman on February 19, 2015, 02:07:17 PM
Is this strictly with running LISP routines, or is it commands and operations in general?  If the former, there could be some leftover references (previous settings, temporary lists, etc.) which aren't cleaned up properly.
Once it starts, it has a lag for everything. LISP being the cause is nothing more than a wild guess.

It's as if I've hit my quota of executed commands, then it gets laggy (while commandline is on). Pretty much, after 5-10 minutes of working on a job, I'll have to close the commandline.
While selection does incur a lag, the commandline (printing text or entering in) becomes sluggish. I was plotting a few easements in my base file the other day, when I noticed it couldn't keep up with me and completely exited out of the core civil 3d line by bearing command.
Logged
Civil 3D 2019 ~ Windohz 7 64bit
Dropbox

Lee Mac

  • Seagull
  • Posts: 12912
  • London, England
Re: Significant commandline lag
« Reply #14 on: February 19, 2015, 04:49:32 PM »
Does a (gc) have any effect? - Just a stab in the dark.
Logged

alanjt

  • Needs a day job
  • Posts: 5352
  • Standby for witty remark...
Re: Significant commandline lag
« Reply #15 on: February 19, 2015, 05:38:11 PM »
Quote from: Lee Mac on February 19, 2015, 04:49:32 PM
Does a (gc) have any effect? - Just a stab in the dark.
Worth a shot. Next time it happens, I'll try that.
Logged
Civil 3D 2019 ~ Windohz 7 64bit
Dropbox

alanjt

  • Needs a day job
  • Posts: 5352
  • Standby for witty remark...
Re: Significant commandline lag
« Reply #16 on: February 23, 2015, 10:58:19 AM »
(gc) did nothing. The only fix I have found is to close cad and reopen the drawing. This works for an unknown amount of time and goes back to lagging. Close commandline has been the only TRUE fix.

Found this while doing another search this morning: http://forums.autodesk.com/t5/autocad-civil-3d-general/2013-civil-3d-memory-leak/td-p/3648504/page/2
Logged
Civil 3D 2019 ~ Windohz 7 64bit
Dropbox

Rob...

  • King Gator
  • Posts: 3824
  • Take a little time to stop and smell the roses.
Re: Significant commandline lag
« Reply #17 on: February 23, 2015, 11:00:27 AM »
It really sounds like a cache issue of some sort but I wouldn't know how to fix it without a bit of research.
Logged
CAD Tech

alanjt

  • Needs a day job
  • Posts: 5352
  • Standby for witty remark...
Re: Significant commandline lag
« Reply #18 on: February 23, 2015, 11:26:54 AM »
Logged
Civil 3D 2019 ~ Windohz 7 64bit
Dropbox

Matt__W

  • Seagull
  • Posts: 12955
  • I like my water diluted.
Re: Significant commandline lag
« Reply #19 on: February 23, 2015, 01:15:07 PM »
What about Command Line VS. Text Screen.  Any difference there??
Logged
Autodesk Expert Elite
Revit Subject Matter Expert (SME)
Owner/FAA sUAS Pilot @ http://skyviz.io

alanjt

  • Needs a day job
  • Posts: 5352
  • Standby for witty remark...
Re: Significant commandline lag
« Reply #20 on: February 23, 2015, 01:46:58 PM »
Quote from: M@yhem on February 23, 2015, 01:15:07 PM
What about Command Line VS. Text Screen.  Any difference there??
What do you mean?
Logged
Civil 3D 2019 ~ Windohz 7 64bit
Dropbox

mjfarrell

  • Seagull
  • Posts: 14444
  • Every Student their own Lesson
Re: Significant commandline lag
« Reply #21 on: February 23, 2015, 02:11:35 PM »
I think F2
Logged
Be your Best


Michael Farrell
http://primeservicesglobal.com/

Matt__W

  • Seagull
  • Posts: 12955
  • I like my water diluted.
Re: Significant commandline lag
« Reply #22 on: February 23, 2015, 02:31:45 PM »
Yup
Logged
Autodesk Expert Elite
Revit Subject Matter Expert (SME)
Owner/FAA sUAS Pilot @ http://skyviz.io

alanjt

  • Needs a day job
  • Posts: 5352
  • Standby for witty remark...
Re: Significant commandline lag
« Reply #23 on: February 23, 2015, 02:46:57 PM »
Quote from: M@yhem on February 23, 2015, 02:31:45 PM
Yup
That works fine. Currently, I'll close the commandline, hit F2 (displays on 2nd monitor), and go back to work.
Logged
Civil 3D 2019 ~ Windohz 7 64bit
Dropbox
Pages: 1 2 [All] |   Go Up
« previous next »