Anything you can't do on a Linode?
Memory, CPU and disk space are automatically limited, so you'll know if you're over-consuming when your Linode is acting sluggish.
Any type of software is allowed, too, as long as you secure it good enough to not let people exploit your server (which can quickly turn into something illegal/abusive).
So basically, anything that doesn't spam, sends out malware/spyware/virii or does (or wildly distributes) anything illegal goes. More or less.
EDIT: nevermind, the links were at the bottom of the page. Hehe, duh
I think even one system running this would slow things down, and if everybody did, nothing would get done.
But I think the Linode host looks at a higher level than that. It hands out CPU cycles based on machines, not priorities within the machine. (Corrections welcome, caker or anybody else.) So even if you're running it low priority on your machine, it's hogging everything it can on the host.
> May 20 18:54:23
May 20 18:55:05
The program I'm running isn't exactly a client, but it's a program that I'm running on a few machines which uses as much CPU as it can… presumably there's CPU throttling on a VDS though.
May 20 18:55:15
Like Seti@Home, or distributed.net ?
May 20 18:55:19 * Efudd notes if you are on host6, no!
May 20 18:55:33
I'm matrix.theblob.org on host15 if you want to monitor the usage.
May 20 18:55:34
I'd prever you don't on any host …
May 20 18:55:41
but there's no strict rule against it
May 20 18:55:48
it might get you nice'ed down, though :)
May 20 18:57:03
Ciaran: if it consumes all CPU, I really don't need to look at it
May 20 18:57:41
Okay then. Would it be okay if I renice'd it to something like 15?
May 20 18:57:46
Or 20, even, heh.
May 20 18:57:57 * Efudd would personally hack in a new number "42"
May 20 18:57:59
nice only affects processes inside your Linode
May 20 18:58:24
and nice'ing it would only give CPU time to other processes inside your node, but you'd still be at 100%
May 20 18:58:30
May 20 18:58:37
ciaran, i would have to bet that running within a shared environment isn't your best option
May 20 18:58:41
Right there is some minimal slowdown. By minimal I mean maybe like 1%. I do see what you're getting at though. In a UML enivronment I'm not entirely sure how the behavior is gonna be. One possible way around it though is to cap how much CPU F@H uses. Set it to use 25% max ;) Again though, I guess it could behave different even like this, but I'm sure many people run things constantly on their linodes. There's gotta be a way :)
My understanding is this..
The low priority means it'll step aside for tasks in your instance, but since your instance as a whole is trying to keep the CPU busy at all times, it interferes with CPU bursting of other linode instances on the same host.
Basically, if all of the other linodes on the host are relatively idle, a task of yours can burst up to nearly the full CPU capability of the machine. If 5 other people are running something like S@H or F@H, then your maximum burst is up to 1/6 of the host's CPU. Most server tasks tend to be bursty, only springing into action when a request is made (web request, incoming mail, etc). Therefore it does indeed degrade the performance for your neighbors.
If I've understood UML correctly, that is. Someone correct me if I'm wrong.
SETI or Folding would destroy that. Please don't run them!
Okay so if i keep the max CPU resources for F@H down below the guaranteed CPU set aside for my linode, that should be fine right? What I don't understand (from the IRC chat posted) is how can a process set to use a fraction of CPU time max still use 100%? Granted I'm referring to setting the limit using the prog itself (as F@H supports this internally). I doubt I'll ever run F@H on my linode, I just don't understand why this would be a prob if your capping what the prog can use to begin with. If your running within your guaranteed limits for CPU, it shouldn't slow down the host. UML is new to me in case you guys didn't figure it out already
Think about it this way:
You've got a slice of the pie DEDICATED to you. You can use that slice, and ANY process you run has priority over it.
If that slice is idle, then other people can 'borrow' it for short times for CPU intensive apps. The fact that everyone will not be using 100% of their slice at all times helps to make UML a bit better.
If you run some dist. computing client, you'll end up using your slice 100% of the time, and possibly even 'borrowing' some other people's slices who aren't using theirs.
I think, if nothing else, it would be HIGHLY impolite to others on your host.
So, basically, if you're on host40, and you do this, I will track you down
Having said that, I run an IRC server linked to a very small network (only about 3-4 nodes) ans haven't been a victim. But then, I know all the people who use that network, and it's not a public one.
Will all the above plus the basics (LAMP) be able to run fine together on a Linode64?
It should be able to handle it so long as you trim down on the Apache modules as well as you MySQL configuration (check
iocount=24689 iorate=0 iotokens=400000 tokenrefill=512 token_max=400000
Seems pretty good