cLAW: Long delays and eventual crashes?

[NObama]

Seeing from your logs, you are looting a billion items at a setting and the logging gets kinda long.

Indeed.  Indeed I am.  MUAHAHAHAHAHA!

*ahem*  Sorry about that - channeled a bit of Dr. Evil for a moment.

I appreciate all the effort to review the log files to find a solution!  I'll let you know after my run tonight if the log option/commenting works.  First, though, I have ANOTHER BILLION ITEMS to sort.

MUAHAHAHAHA!

*ahem*

[TrailMyx]

let it run for a while with that code commented out and send another var dump to see if that's helping or not.  It's been a while since I've played with the CLAw (or any script for that matter) so there could be other issues.

don't forget to check the LPC.  If the LPC is too high on the honor and attack script, that will impact the speed that the CLAw loots.

[manwinc]

On Newer Processors you also have to be careful with the ol LPC. With a lot of things in game the difference between 20 and 100 LPC is negligible. Even 20 and 1000 is almost non existent for most applications, but it will Increase your CPU regardless. The Higher your CPU goes, the Slower your Scripts go, no Matter your LPC.

[TrailMyx]

True true.  EUO scripts basically share an LPC pool.  If you have one script that's constantly running at high LPC, it will detract from the other scripts performance.

[manwinc]

And if all else fails you might have to switch from using a "Call" to actually incorporating the script into your code at the bottom and then using a gosub. Calls take longer.

[TrailMyx]

also very true.  I switched from calls to gosubs years ago.  I found their stability would cause EUO to crash when I would run the calls based files from a NAS.  Just made everything unstable.  But after I got rid of those calls, the scripts would run forever.

[Endless Night]

also very true.  I switched from calls to gosubs years ago.  I found their stability would cause EUO to crash when I would run the calls based files from a NAS.  Just made everything unstable.  But after I got rid of those calls, the scripts would run forever.

LOL, im going the otherway ... I'm moving everything into calls.... and loving it...

With the buffbar i did some testing on calls.... the slow down from using a call is minimal for all but the most time sensitive scripts.  And interestingly if you call a script more that a couple times a second their is basically zero load time.. probably because the drive still has it in its cache. 

So far no I've had zero problems with my call library and from some of my scripts the librarys are calling themselfs....... but my files are all local.   The only bit that can be tricky about calls is debugging.

[TrailMyx]

The stability issue for me was a deal-breaker since I script completely from my Samba shared drive.

[Endless Night]

The stability issue for me was a deal-breaker since I script completely from my Samba shared drive.

Yea i can how that would be an issue...  but right now im going to take the drawback of not being ale to use a network drive over the benifit of not having a 100 version of my code all over the place.

[manwinc]

 

The stability issue for me was a deal-breaker since I script completely from my Samba shared drive.

but right now im going to take the drawback of not being ale to use a network drive over the benifit of not having a 100 version of my code all over the place.

I hit that point a while back with a lot of my scripts because I kept having to update the Individual Subs in 20 Scripts every Time I found a glitch. But, its 10x more Difficult to debug a script when its in call mode as well, so for that reason I went back to having the code in the scripts themselves. Maybe 1 Day, in the Far off Future I'll have a call Library that I can build my scripts from, but for now everything is still evolving too fast for that.

[TrailMyx]

Back before EUO 1.5, you could actually successfully debug called scripts.  Cheffe just kinda gave up on 1.5 and never debugged the debugging process.