Reputation
Top tag
Next privilege 100 Rep.
Edit community wikis
Badges
6
Newest
 Commentator
Impact
~2k people reached

Jan
23
comment Does IP fail-over help me?
You can put both services into a linux container and expose the service on whatever port you want on the host machine. Additional ip addresses are not necessary.
Dec
21
awarded  Commentator
Dec
21
comment AWS Route 53 Latency Based service for non AWS Instances
I'm not clear on one thing here, does it route based on the estimated latency from the end-user to your external European location, or does it use the estimated latency to eu-west-1 that you supplied when configuring it?
Jul
25
comment What is ECC ram and why is it better?
I'm just waiting for an unscrupulous company to claim their accounting fraud was actually just a bit error.
Jul
16
comment Is it possible to limit/throttle page faults with LXC container virtualization?
The dominating cost of a page fault (when swapping) is the page read. Whether throttling that hurts the system overall very much depends on the implementation. The "sane" way of doing it is to trigger a context switch when a process reaches its IO limit, e.g. sleep for 10ms to simulate the cost of swapping. In that case the system becomes fairer because compute resources go to well-behaved processes instead. See OpenVZ vswap for an implementation of swap throttling (and I doubt it's a communist-style implementation either.)
Jul
10
comment Is it possible to limit/throttle page faults with LXC container virtualization?
That's still presumptuous, I can take two enterprise 250K IOPS SSDs, stick them in the PCI slots and get half a million random 4K page reads per second. I think for a lot of systems that would be more than acceptable. It's not even that exotic, I can get one fifth of that on the high IO AWS instances. It neither needs to come at a high performance cost nor be temporary. Adding delays would hurt the throttled container, but it prevents that same badly behaved container from hogging the entire system.
Jul
10
awarded  Editor
Jul
10
revised Is it possible to limit/throttle page faults with LXC container virtualization?
added 323 characters in body
Jul
8
awarded  Promoter
Jul
8
comment Is it possible to limit/throttle page faults with LXC container virtualization?
Using, e.g. blkio.weight would seem to be exactly what I want, except I don't know if that includes IO generated by page faults (and nowhere does anyone seem to answer that question.)
Jul
8
comment Is it possible to limit/throttle page faults with LXC container virtualization?
Will limiting IO limit page faults as well? Saying there's never a reason to use swap is a little presumptuous don't you think? There are plenty of valid reasons to use swap. I also don't buy your argument that limiting page faults is intrinsically bad. When a cgroup exceeds its limit for a time period, simply suspend it's processes until the end of the time period if they page fault (unless there's spare capacity.) Granted that may be hard to do depending on implementation details in the kernel, I don't know, but I might give it a try if there's no easier alternative.
Jul
6
asked Is it possible to limit/throttle page faults with LXC container virtualization?
Oct
26
comment Directory in /var/run gets deleted after hard reboot
And of course this means the startup script must run as root to be able to write directly to or create a directory in /var/run. Which is annoying...
Oct
26
awarded  Supporter
Oct
12
awarded  Teacher
Jan
23
comment How to tell if a motherboard is UMA or NUMA?
The way I understand it, questions about servers by professionals for professional use are the exact domain of this website.
Jan
23
comment How to tell if a motherboard is UMA or NUMA?
This is not off-topic according to the faqs... Does someone want to explain why this question is not appropriate here?
Jan
22
asked How to tell if a motherboard is UMA or NUMA?
Jun
15
awarded  Student
Jan
5
asked Database checksum features - redundant? useful?