New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
To make it easy, just don't torrent.
Have a great day.
Nope, I do not torrent, just wordpress website for client and a python script to run auto backup by tar/zip command and auto transfer to hubic
I do believe I told you to have a great day.
then, thank you
Nixstats? Disk I/O is monitored and you can set triggers to alert you. You'd probably be better off just optimizing your setup so it doesn't abuse I/O - or finding another provider.
What's the torrent clieny you're using?
rtorrent, for example, has a way to limit I/O usage, you should limit it there.
I'm not using the VPS for torrent related services.
do you have any invitation code?, just shot those guy an email and waiting for an invite
If memory serves me correctly and in all honesty I'm probably wrong, the invitation code was LET.
EDIT: Yup it's LET
Thats very rude.
Only if you have no sense of humour. May I count you among the unfortunates who have this terrible affliction?
Maybe consider using rsync as well do do incremental backups, no properly setup Wordpress site should generate abuse amounts of IO, it's usually some crappy third party plugin causing the issue.
NIXStats can monitor I/O usage unless you're on an openvz instance. On openvz you will be able to see process level I/O usage tho.
you can use nodequery .com as well
Isolation of disk i/o resource usage in the Linux kernel is still not well developed.
Best results are achieved using cgroups imho.
You can monitor disk usage with munin.
Run your commands with nice and ionice before them
nice -n19 ionice -c2 -n7 tar (blah blah)
It will only reduce load/ioload relative to your container but it should help slow down the program to reduce the overall effect.
If you have cpanel you can also add cpuwatch to that
cpuwatch 1 nice -n19 ionice -c2 -n7 tar (blah blah)
which will pause the program if the load goes over 1 and resume afterwards
Monit can do this. Just make a rule that when the disk IO Wait is > 80% for more than 5 minutes kill the process. If IO Wait isn't accurate enough make a script to parse sysstat that Monit can use.
You on openvz? and the provider uses nodewatch?