I had no idea the performance of Slash was so low. Apache itself ought to sail, even on an "older" box like that. I just installed YDL on a G3-upgraded PCP 210 with 128 MB to use as a test box for Slash. Now it's sounding like I could max that out just clicking around the site myself.
How much benchmarking and optimization is done on Slash? Is there documentation on tuning and tweaking for low-end systems like the poster and myself have? I bet there is demand for a "mature" discussion board system for low-traffic sites that could otherwise get away with hardware like this. I knew that hoping my box could serve/.-like loads was unreasonable, but I really thought it would be able to handle a MacSlash-level load.
I don't mean this as a slam on any of the Slash developers. I really like it's capabilities. I'm just unfamiliar with the system requirements.
I had no idea the performance of Slash was so low.
It isn't. Please don't confuse "memory-hungry" with "low performance". That's like saying a sports car is low performance because it runs best on high-octane gas.
I just installed YDL on a G3-upgraded PCP 210 with 128 MB to use as a test box for Slash.
If you don't tune the parameters, perhaps. Limit the numbers of httpds, mysql threads, and cut back on the caching vars in Slash.
Sounds like the primary limit (in terms of pressing a dusty retired workstation back into service) to running Slash is RAM. The recommended minimum PII-200 probably has a ≥1 GB HD, but didn't come with 256 MB of RAM. Maybe it would be best to just put another couple sticks in my box.
That's really the best option. RAM is cheap, and almost all machines can accommodate 256MB or more. 256 is the bare minimum I'd want on a live machine, but you could get away with 128 if you tuned everything well, didn't have a ton of traffic, and didn't use the machine for anything else.:) But pudge.net runs on 256MB, and it is fine (once I tuned it in a few places here and there).
Primary place to tune: # of Apache processes, # of MySQL threads, and cache variables (esp. template cache). Also, once you get a feel for how much RAM a typical Apache process takes for you, use Apache::SizeLimit to make sure it doesn't get too big.
egads (Score:1)
I had no idea the performance of Slash was so low. Apache itself ought to sail, even on an "older" box like that. I just installed YDL on a G3-upgraded PCP 210 with 128 MB to use as a test box for Slash. Now it's sounding like I could max that out just clicking around the site myself.
How much benchmarking and optimization is done on Slash? Is there documentation on tuning and tweaking for low-end systems like the poster and myself have? I bet there is demand for a "mature" discussion board system for low-traffic sites that could otherwise get away with hardware like this. I knew that hoping my box could serve /.-like loads was unreasonable, but I really thought it would be able to handle a MacSlash-level load.
I don't mean this as a slam on any of the Slash developers. I really like it's capabilities. I'm just unfamiliar with the system requirements.
⇒ Constitutionally Correct [cpne.org] ⇐
Re:egads (Score:2)
It isn't. Please don't confuse "memory-hungry" with "low performance". That's like saying a sports car is low performance because it runs best on high-octane gas.
I just installed YDL on a G3-upgraded PCP 210 with 128 MB to use as a test box for Slash.
If you don't tune the parameters, perhaps. Limit the numbers of httpds, mysql threads, and cut back on the caching vars in Slash.
Re:egads (Score:1)
You are, of course, correct. Sorry I mis-spoke.
Sounds like the primary limit (in terms of pressing a dusty retired workstation back into service) to running Slash is RAM. The recommended minimum PII-200 probably has a ≥1 GB HD, but didn't come with 256 MB of RAM. Maybe it would be best to just put another couple sticks in my box.
⇒ Constitutionally Correct [cpne.org] ⇐
Re:egads (Score:2)
Primary place to tune: # of Apache processes, # of MySQL threads, and cache variables (esp. template cache). Also, once you get a feel for how much RAM a typical Apache process takes for you, use Apache::SizeLimit to make sure it doesn't get too big.
Parent