|
The capacity is about the same: if you have a single website on a single VP=S or dedicated server, you will be able to handle approx the same load with= 6.2 or with 7
WebDNA 7.0 allows you to use very fast and light webservers like lighttpd: =this webserver can handle without effort two to three times more simultaneo=us hits than apache: apache is RAM hungry, usually includes a lot of module=s and the http transactions are heavier than with lighttpd for instance. Li=ghttpd with WebDNA 7.0 would probably be faster than apache with WebDNA 7.0= or 6.2.
Another point is if you run several websites on a single box, WebDNA 6.2 wi=ll handle all of them and if one website is buggy or takes all the resource=s, then WebDNA 6.2 might slow down, hang or even crash. If it crashes, it c=rashes apache too.
If you run one WebDNA 7.0 copy per website, a buggy or hungry website will =just slow or crash its WebDNA copy. It will not crash apache, it will not c=rash the other WebDNA copies. You would be able to fix the problem by just =working on the faulty website, without holding the service for your other c=ustomers.
Also, by monitoring the CPU load (using the "top" command), you w=ould immediately be able to "see" what website is taking more res=ources than the others, and what is the real RAM usage per website.
Finally, there is no need to restart WebDNA if it crashes: apache (or any o=ther webserver software) takes care of it.
DOWNLOAD WEBDNA NOW!
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...