Re: [WebDNA] Serial numbers and pricing for WebDNA 7.0
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106105
interpreted = N
texte = Hi Govinda! few comments. I just would like to compare a WebDNA database = with a MySQL database, for about the same amount of records (83,000 with = 38 fields, some of them being long text descriptions): 24MB with WebDNA, = 186MB with MySQL. Also, the new FastCGI version can work on a dedicated backend server = with several front end web servers taking care of static objects. We did some testing a year ago and a lookup with WebDNA compared to = MySQL was running 50 times faster. A classic search was 5 to 10 times = faster. www.webdna.us might be slow because there are many redirections. It is = also an old 6.0 version running on 1GHz multiprocessors server: = performances are not affected by load, but it is not very fast. We will continuously support WebDNA, releasing quick fixes if necessary. I hope all these informations will give you a base to make your = decision. have a great weekend! - chris On Jan 22, 2011, at 14:09, Govinda wrote: >>=20 >> WebDNA is a pretty stable and mature product. There will be updates = if we can further improve it, or even new versions if some interesting = new features are suggested. I just don't want to fall into the Microsoft = or Adobe policy which is to add a new version every year just to make = customers feel they need it, but finally get disappointed because there = is nothing really new. >=20 >=20 > Hi Chris! >=20 > Your comment above was good and thought-provoking too. >=20 > I am have one big new project coming up and am torn between doing it = in Webdna (what is faster, what I know thoroughly, and what I love) = versus doing it in PHP (which I want to learn ever more because I get = work in it and because it is so commonplace). But anyway the only real = main reason I am hesitant to use Webdna is because I am expecting the = new site to become extremely busy at some point and the central = databases to become huge (in the GBs). Webdna does have all the tools I = would need, but the one area I have not been 100% confident is in = watching people complain off and on over the years that when a site gets = 'too much' traffic.. and when there is *a lot* of RAM db activity.. then = their site comes to a crawl (like maybe this is even what is making the = http://www.webdna.us site so slow?), or worse yet Webdna has to be = restarted regularly. Perhaps all these years it was always due to some = memory leak that has meanwhile been fixed in v.7? (like for example it = took one of my clients until a few months ago to discover that one = achilles heel in her site was [appending] records by the thousands (even = to a purely RAM [table]!) caused Webdna to hang). I am nervous about = being the new guinea pig. I wold feel somewhat more confident about it = if I knew that the SQL tags were 100% mature and robust, so that I could = make my HUGE dbs in SQL (maybe MySQL) .. but I have never used SQL = outside of PHP and I am not even sure Webdna's SQL tags are current. = Are they? For MySQL? Are you, or is anyone here, using them for real = *large/heavily-trafficked* mission critical projects? >=20 > ------------ > Govinda >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list
. > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
Associated Messages, from the most recent to the oldest:
Hi Govinda! few comments. I just would like to compare a WebDNA database = with a MySQL database, for about the same amount of records (83,000 with = 38 fields, some of them being long text descriptions): 24MB with WebDNA, = 186MB with MySQL. Also, the new FastCGI version can work on a dedicated backend server = with several front end web servers taking care of static objects. We did some testing a year ago and a lookup with WebDNA compared to = MySQL was running 50 times faster. A classic search was 5 to 10 times = faster. www.webdna.us might be slow because there are many redirections. It is = also an old 6.0 version running on 1GHz multiprocessors server: = performances are not affected by load, but it is not very fast. We will continuously support WebDNA, releasing quick fixes if necessary. I hope all these informations will give you a base to make your = decision. have a great weekend! - chris On Jan 22, 2011, at 14:09, Govinda wrote: >>=20 >> WebDNA is a pretty stable and mature product. There will be updates = if we can further improve it, or even new versions if some interesting = new features are suggested. I just don't want to fall into the Microsoft = or Adobe policy which is to add a new version every year just to make = customers feel they need it, but finally get disappointed because there = is nothing really new. >=20 >=20 > Hi Chris! >=20 > Your comment above was good and thought-provoking too. >=20 > I am have one big new project coming up and am torn between doing it = in Webdna (what is faster, what I know thoroughly, and what I love) = versus doing it in PHP (which I want to learn ever more because I get = work in it and because it is so commonplace). But anyway the only real = main reason I am hesitant to use Webdna is because I am expecting the = new site to become extremely busy at some point and the central = databases to become huge (in the GBs). Webdna does have all the tools I = would need, but the one area I have not been 100% confident is in = watching people complain off and on over the years that when a site gets = 'too much' traffic.. and when there is *a lot* of RAM db activity.. then = their site comes to a crawl (like maybe this is even what is making the = http://www.webdna.us site so slow?), or worse yet Webdna has to be = restarted regularly. Perhaps all these years it was always due to some = memory leak that has meanwhile been fixed in v.7? (like for example it = took one of my clients until a few months ago to discover that one = achilles heel in her site was [appending] records by the thousands (even = to a purely RAM [table]!) caused Webdna to hang). I am nervous about = being the new guinea pig. I wold feel somewhat more confident about it = if I knew that the SQL tags were 100% mature and robust, so that I could = make my HUGE dbs in SQL (maybe MySQL) .. but I have never used SQL = outside of PHP and I am not even sure Webdna's SQL tags are current. = Are they? For MySQL? Are you, or is anyone here, using them for real = *large/heavily-trafficked* mission critical projects? >=20 > ------------ > Govinda >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
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:
[WebDNA] Authorize.net and [tcpconnect] (2016)
#uck you (1998)
more on quicktime test stuff (1997)
HTML encoding in URLs (1997)
How to break a search ... (2002)
[redirect] question (2005)
Different Tax levels (1998)
affiliate marketing program (1998)
[WriteFile] problems (1997)
Alternating BGColors in Table Rows (1998)
Re[2]: 2nd WebCatalog2 Feature Request (1996)
Associative lookup style? + bit more (1997)
carriage returns in data (1997)
Newbie trouble with [url] & [foundItems] (2000)
Email (1998)
Dark Horse Comics success story (1997)
Mail Server Needed. (1998)
Email address checker (2002)
Trunk-gator (1997)
Hiding HTML and breaking the page (1997)