Finally i got around to buying a vps. Not having used linux before yesterday many of these values are new to me and they may need tweaking compared to the guides i found on the net and on this site. I hope you more experienced users.
CPU speed is good, its a new server and there are only 2 vps accounts on the server. So far.
Not sure what tweaks are a must, but i read somewhere that unused ram are wasted ram. Dont want that. But im not sure my current needs can use all the ram.
max_execution_time = 30 ; Maximum execution time of each script, in seconds max_input_time = 60 ; Maximum amount of time each script may spend parsing request data ;max_input_nesting_level = 64 ; Maximum input variable nesting level memory_limit = 128M ; Maximum amount of memory a script may consume (128MB) session.gc_maxlifetime = 1440 post_max_size = 8M
; Same as aboves but for variable cache ; If you don't know for sure that you need this, you probably don't xcache.var_size = 256M xcache.var_count = 1 xcache.var_slots = 8K xcache.var_ttl = 0 xcache.var_maxttl = 0 xcache.var_gc_interval = 300
; N/A for /dev/zero xcache.readonly_protection = Off
xcache.mmap_path = "/dev/zero"
xcache.cacher = On xcache.stat = On
read_buffer = 16M write_buffer = 16M
I would love your expert opinion on how to optimize these settings according to the vps limits.
max_connections is (again) simultaneous connections.
Every client that connects will use those *_buffer_sizes. They total 4M. So you're saying it's OK to use up to 400 * 4M = 1600M of memory for clients. Are you sure you want that?
Consider bringing max_connections down -- to maybe 50-100.
By setting this limits to realistic values you help ensure that your VPS won't crash for lack of memory. Always calculate based on your guaranteed memory. Ignore 'burst memory' as it simply may not be available for you to use.