Re: [WebDNA] WebDNA code validator
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 107148
interpreted = N
texte = Hi Daniel! On Jul 29, 2011, at 13:49, Daniel Meola wrote: > Finally, I can only assume that at some point a single server can only = handle so much traffic. Perhaps we have reached that point. Has anyone = successfully set up load balancing across multiple WebDNA servers?=20 If you are in the situation where you write to databases, you can't (at = this time) sync multiple servers databases loaded in RAM, though we will = work on a solution in the future. If you just "read" a database, then = yes, you can run multiple servers with the same content. One solution = could be to to route the "read" requests to a round robin cluster of = servers and route the "write" requests to a single server, whose = database content would be regularely copied to the read-only boxes. = Google is using something like this. Another solution is to run several = dedicated front-end web servers and one dedicated WebDNA 7.0 FastCGI = back-end server: this will work. However, carefully coded WebDNA website running on a high speed CPU with = lighttpd (faster, smaller footprint and faster FastCGI interface than = apache) and WebDNA 7.0 will handle a very high load without any problem = (faster than the same hardware with php + MySQL). Speed problems arise = with badly designed complex search commands, or if you write a lot to = your disk. For instance, if you use [append] against a large database, = it will rewrite the entire database to disk after each single [append]. - chris=
Associated Messages, from the most recent to the oldest:
Hi Daniel! On Jul 29, 2011, at 13:49, Daniel Meola wrote: > Finally, I can only assume that at some point a single server can only = handle so much traffic. Perhaps we have reached that point. Has anyone = successfully set up load balancing across multiple WebDNA servers?=20 If you are in the situation where you write to databases, you can't (at = this time) sync multiple servers databases loaded in RAM, though we will = work on a solution in the future. If you just "read" a database, then = yes, you can run multiple servers with the same content. One solution = could be to to route the "read" requests to a round robin cluster of = servers and route the "write" requests to a single server, whose = database content would be regularely copied to the read-only boxes. = Google is using something like this. Another solution is to run several = dedicated front-end web servers and one dedicated WebDNA 7.0 FastCGI = back-end server: this will work. However, carefully coded WebDNA website running on a high speed CPU with = lighttpd (faster, smaller footprint and faster FastCGI interface than = apache) and WebDNA 7.0 will handle a very high load without any problem = (faster than the same hardware with php + MySQL). Speed problems arise = with badly designed complex search commands, or if you write a lot to = your disk. For instance, if you use
[append] against a large database, = it will rewrite the entire database to disk after each single
[append]. - chris=
christophe.billiottet@webdna.us
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
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...
Related Readings:
allow or deny based on referer.... (1997)
wierd crashes for multi-sendmails on NT (1997)
webmerchant/mac auth. rejects zipcode (1998)
Re(2): Forcing Search w/ URL (1999)
Random Command (1997)
ShowNext Context (2004)
WebCatalog 2.0 & WebDNA docs in HTML ... (1997)
[WebDNA] Hosting WebDNA on a shared hosting account (2016)
Newbie problem blah blah blah (1997)
orders with blanks or [xxx] literal text (2000)
Setting up WebCatalog with Retail Pro data (1996)
WCS Newbie question (1997)
WebCatalog 3.0.8 is on FTP... (2000)
[shownext max=?] armed (1997)
Monthly Reports (2000)
WebTen and WebCat (1997)
Indexing Web sites? (2000)
two of the same named db's open at once (1998)
billing system (2003)
Unexpected error (1997)