14:54 < harry> Enable Hard CPU Limits 14:54 < harry> Avoid idle CPUs by skipping Time 14:54 < harry> Limit the IDLE task 14:54 < beuss> I tries 3 days ago but it wasn't working so I gave up and put everything on the same partition 14:54 < harry> which ones should i enable? 14:54 < harry> ? 14:54 < harry> beuss: just put it in the fstab of the guest 14:55 < harry> etc/vservers//fstab 14:55 < beuss> � fait 2 jours qu'il est l�dessus I tried but secure-mount was complaining about unauthorized mount 14:55 < beuss> sorry messed up with two sentences 14:55 < harry> hehe 14:56 < harry> daniel_hozac: do you know what i should enable... and why? what's the advantage of which choise? 14:56 < harry> Enable Virtualized Guest Time ==> enable or disable? and why? 14:58 -!- chand [~chand@m167.net81-64-156.noos.fr] has joined #vserver 15:03 < harry> hmm... silence 15:03 < harry> it would be nice to have a clue wether it's best/normal to put it ON or OFF 15:03 -!- mire [~mire@24-166-222-85.adsl.verat.net] has quit [Quit: Leaving] 15:03 < harry> This option allows the scheduler to artificially advance time (per cpu) when otherwise the idle task would be scheduled, thus keeping the cpu busy and sharing the available resources among certain contexts. 15:03 < harry> is this a good thing, to artificially do that? 15:04 < harry> i'd say... how the hell should i know 15:04 < harry> does it make my system go faster/slower/more reliable? 15:04 < harry> Limit the idle slices, so the the next context will be scheduled as soon as possible. This might improve interactivity and latency, but will also marginally increase scheduling overhead. ==> what should one do... for "normal" systems 15:04 < harry> when on, when off