>
> Last I tried (in 2.4), sparse swapfiles were a no-no.
Well I definitely wont do that!
Its not really a problem anyway, as I can monitor this based on IO
disk activity (I suppose).
---
SF email is sponsored by - The IT Product Guide
Read ho
--- Gordon Russell <[EMAIL PROTECTED]> wrote:
> Yes, swap is huge (300 MB). But it never gets used
> unless you do a yum
> upgrade (which needs 200 MB!). Noone has tried this
> yet, but I can
> monitor that by creating the swap with sparse blocks
> and using du.
Sparse swap files are the recipe
On Thu, 24 Feb 2005, Gordon Russell said:
> monitor that by creating the swap with sparse blocks and using du.
Last I tried (in 2.4), sparse swapfiles were a no-no.
--
> ...Hires Root Beer...
What we need these days is a stable, fast, anti-aliased root beer
with dynamic shading. Not that you can
[EMAIL PROTECTED] said:
> I am having real problems with what appears to be scheduling issues,
> and I am running out of ideas...
Why do you think they are scheduling issues?
> We have a cluster of 5 machines, each running about 15 UMLs. Things
> seem to run great for a while, then performance of
> With 15 guests per host, could you be running yourself out of physical
> memory?
Nope. 64 MB per host. I have not had more than 10 per machine so far,
so thats 640MB used out of 1 GB. I am using tmpfs too...
Yes, swap is huge (300 MB). But it never gets used unless you do a yum
upgrade (which
On Thu, 24 Feb 2005, Gordon Russell wrote:
> We have a cluster of 5 machines, each running about 15 UMLs. Things
> seem to run great for a while, then performance of the UMLs seems to
> die for a while.
> --snip--
> Machines are all 1GB or better, 2GHz or better, on a 0.1GB network
> backbone.
W
> [EMAIL PROTECTED] said:
> > I am having real problems with what appears to be scheduling issues,
> > and I am running out of ideas...
>
> Why do you think they are scheduling issues?
Thats a good question!
More or less just speculation.
If someone does something CPU heavy, and I nice them to 20
I am having real problems with what appears to be scheduling issues,
and I am running out of ideas...
We have a cluster of 5 machines, each running about 15 UMLs. Things
seem to run great for a while, then performance of the UMLs seems to
die for a while.
My solution to this was to look at all ru