DrHouse wrote:That's only true for linux, since on windows you use it for nothing.
Go to startGameServer.bat and edit it in the same way
god damn, thank u man
).
just one, possibly stupid question ,still ,
also i found this info
rem Make sure -Xmn value is always 1/4 the size of -Xms and -Xmx.
rem -Xms and -Xmx should always be equal.
rem 2GB: -Xmn256m -Xms1024m -Xmx1024m
so , if i set
xms/xmx to 2048 / xmn 512, that s 2 GB of ram,that means java will grow max to 2GB? i `m just wondering why it doesnet behave like any other application, and just grows and uses even the slower pagefile if needed, instead of giving errors and maybe overusing the cpu (i`ll see if that was the problem after probabil the next 24 hrs, but sadly i doubt it and still don`t understand why the hack the server lags if the cpu waves to MAX 50%, not 100%..it shouldnt be a problem at 50...i guess)
----
also, what happends when it reaches max? many times i had on win 32 1200 mb used, more then the max 1024 in the gameserver.bin xmn/xms . Do people get disconeccted when the memory is almost full, as in (IO/ERROR user xxx disconected by the software in your machine)?
also there is the mythical theadpool. on many topics here, some mod wrote that the threadpool values should be a number equal to your proc/core numbers in your system. that means if you have a dual core you should put for exemple 2 to those values.
still, if this explanation is right (and i tried it, works ok with 2) , then why is the default values have such values as 13/4/8 and so on? wouldnt it make sense the default beeing the smalles core number possible, eg: 2 for safety reasons?
something just doesent add up.
this is my thread config,my test systembeeing a dual core 3800(2100)windsor amd 64 with 3gb
Code: Select all
# Default: 10ThreadPoolSizeEffects = 10 # Default: 13ThreadPoolSizeGeneral = 13 # Default: 2UrgentPacketThreadCoreSize = 2 # Default: 4GeneralPacketThreadCoreSize = 4 # Default: 4GeneralThreadCoreSize = 4 # Default: 6AiMaxThread = 6
from wiki
The cost of having a larger thread pool is increased resource usage. The algorithm used to determine when to create or destroy threads will have an impact on the overall performance:
* create too many threads, and resources are wasted and time also wasted creating any unused threads
* destroy too many threads and more time will be spent later creating them again
* creating threads too slowly might result in poor client performance (long wait times)
* destroying threads too slowly may starve other processes of resources
[img]
http://en.wikipedia.org/wiki/File:Thread_pool.svg[/img]
so, having a lower number would mean increased performance, no matter the server... but what are the benefits of having a higher number of threads?
Typically, there are many more tasks than threads. As soon as a thread completes its task, it will request the next task from the queue until all tasks have been completed. The thread can then terminate, or sleep until there are new tasks available.
maybe having the ability to run much more tasks at once...but i`m guessing here, i didnt notice no difference between setting all values abow to 2 instead of the default values wich are much higher..
so again, would it be advised to push the sytem limit by putting higher numbers? the real question is IT IS WORTH IT , practically , for l2j server? is there something to gain?
can`t find good info about this,just people guessing without actually knowing what are they tuning, practically.
)
