SphereServer BugTracker - SphereServer
View Issue Details
0002016SphereServerexecutable - windows buildpublic05-08-11 11:5502-03-14 06:17
trinax 
XuN 
normalmajoralways
resolvedfixed 
 
 
Automated (specify build number)
None
None
1488
0002016: CPU usage drops if I change .ini and resync.
I am testing on my 1.6ghz sc netbook now. Sphere uses up 50% of cpu power (have 2 virtual cores so it is supposed to be 100% and freeze my pc I guess) after it is done loading everything.

When I change sphere.ini (no real modification actually) and resync, cpu usage drops to 25% (september pre-release uses %16 on this machine). Did not seem to work with the resync of normal scripts.

So, does sphere reads some ini settings wrong or something at startup?
No tags attached.
Issue History
05-08-11 11:55trinaxNew Issue
06-08-11 10:43trinaxNote Added: 0001210
06-08-11 10:43trinaxNote Edited: 0001210bug_revision_view_page.php?bugnote_id=0001210#r395
06-08-11 13:17trinaxNote Added: 0001212
06-08-11 14:23trinaxNote Edited: 0001212bug_revision_view_page.php?bugnote_id=0001212#r397
06-08-11 14:26trinaxNote Edited: 0001212bug_revision_view_page.php?bugnote_id=0001212#r398
06-08-11 14:26trinaxNote Edited: 0001212bug_revision_view_page.php?bugnote_id=0001212#r399
02-03-14 06:17XuNStatusnew => resolved
02-03-14 06:17XuNResolutionopen => fixed
02-03-14 06:17XuNAssigned To => XuN

Notes
(0001210)
trinax   
06-08-11 10:43   
Confirmed this to happen on another machine and on rev#1468.

(0001212)
trinax   
06-08-11 13:17   
(edited on: 06-08-11 14:26)
Confirmed on Linux build as a drop from 68% usage to 28% with empty save and account files on amd 2.6ghz x2 64-bit machine. rev#1493.

Still, how come an "absolutely empty, nothing to do, no timers, nothing" server uses up to 28% cpu usage. Seems like sphere needs heavy optimization. (cpu usages taken from "top")

Further feedback:
It may be important that using a fresh install with empty save files. Now, I created a char and teleported around a little and when I restart CPU usage is around 25%.

May be related to 0001811.