search

XiozZe / XioScript

XioScript
11 stars 16 forks source link

XS memory exhaust #84

Open TeaMike opened 8 years ago

TeaMike commented 8 years ago

I've added about 8000 subdivisions now, somewhen after 2000 the loading of settings page, and process of generating, got slower and slower.

XioMaintenance stopped showing movement after 9 min 55 sec; memory usage went up to 2.7 GB and was still raising when, probably after half an hour, i reloaded the page / cancelled the script.

Price setting on 66 gas stations now takes 4 min 16 seconds. Suggestions?

TeaMike commented 8 years ago

i'm still testing; swapping local storage files and adding different subdivision types to figure out the issues.

I will probably end up using XS with 2 or more (depending on script runtime) different local storage files (i don't need animal farms, equipment and some others fixed every day, for example) as it seems somewhat cleaner and definitely faster than the current import/export procedure.

TeaMike commented 8 years ago

only my factories are added to the task list here (the script still ran at this point)

xsdooh

XiozZe commented 8 years ago

XS 12.1 should load considerably less pages, as most actions will be taken from the summarized Equipment, Salary and other Management pages. Price and Supply functions will still need a hard load though. This should reduce the memory needed, and if it's still a problem, I will do something to erase used data from memory.

TeaMike commented 8 years ago

i am fixing prices at stores with XS 10.5 which does it in 2 minutes, running the remaining above takes average 38 minutes (using 10.5 anyway because 12.xx still lacks price fixing for the service enterprises but of course i'll be great if that becomes obsolete). One critical thing is that IF the script hangs somewhere its almost impossible to figure out where it is. I think a fail-save for such hang-ups would be good.

XiozZe commented 7 years ago

I have created a personal Store Supply script, that micro-optimizes all supply of every good, and it took 72 minutes to complete (19 stores). However, it did not seem to have slowed down and although I didn't capture the memory usage, I did not notice anything strange. (The 72 minutes is intentional, and it made close to 10000 server calls.)

TeaMike commented 7 years ago

ok, but what do you mean with it? XS 10.5 fixes prices at my 350 stores in about 2 minutes.

XiozZe commented 7 years ago

I mean: wait and see.

XiozZe commented 7 years ago

Last week my Chrome browser broke multiple times because of memory issues. At least 3.0 GB usage. Funny thing is two weeks ago everything worked perfect (<0.5 GB memory for sure, but I never checked). And I didn't even change my script! Note that I'm talking about my personal store-supply script, running 3 hours on average.

Just boasting, nothing serious, ignore this.

TeaMike commented 7 years ago

it might depend on how many stores you run. I've got 300 and some active ones, would 24 hours be enough for the script to fix it? If so i may consider buying a new computer to dedicate for this.

Just kidding, nothing serious, ignore this.

XiozZe commented 6 years ago

What happens if you try to let XS14 handle 2000 subdivisions?