Re: [WebDNA] Serial numbers and pricing for WebDNA 7.0
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106106
interpreted = N
texte = Yes of course Webdna RAM-based dbs are faster! That I know and love. = Here I am asking about when the dbs get too big ... to a point where one = needs to consider relinquishing them to disk. =20 I am glad you are dedicated to supporting the product! That is cause = for peace of mind for sure! Here is a very important question: How are the SQL tags? Are they current? Bug free? Work with MySQL? Thanks! -Govinda > 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. >=20 > Also, the new FastCGI version can work on a dedicated backend server = with several front end web servers taking care of static objects. >=20 > 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. >=20 > 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. >=20 > We will continuously support WebDNA, releasing quick fixes if = necessary. >=20 > I hope all these informations will give you a base to make your = decision. >=20 > have a great weekend! >=20 > - chris >=20 >=20 > On Jan 22, 2011, at 14:09, Govinda wrote: >=20 >>>=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
Associated Messages, from the most recent to the oldest:
Yes of course Webdna RAM-based dbs are faster! That I know and love. = Here I am asking about when the dbs get too big ... to a point where one = needs to consider relinquishing them to disk. =20 I am glad you are dedicated to supporting the product! That is cause = for peace of mind for sure! Here is a very important question: How are the SQL tags? Are they current? Bug free? Work with MySQL? Thanks! -Govinda > 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. >=20 > Also, the new FastCGI version can work on a dedicated backend server = with several front end web servers taking care of static objects. >=20 > 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. >=20 > 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. >=20 > We will continuously support WebDNA, releasing quick fixes if = necessary. >=20 > I hope all these informations will give you a base to make your = decision. >=20 > have a great weekend! >=20 > - chris >=20 >=20 > On Jan 22, 2011, at 14:09, Govinda wrote: >=20 >>>=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
Govinda
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:
Question about replacing words (1998)
upgrading (1997)
Can't find templaes (1997)
Re:2nd WebCatalog2 Feature Request (1996)
Exclude by date - multiple (1997)
Showif, Hideif reverse logic ? (1997)
[WebDNA] Shopping cart code debug (2009)
OT: Quick poll (2003)
6.1 Patch - Form Data Back Button Issue (2006)
BIAP relay (1999)
hard carriage returns and sendmail (1998)
Mass Mail (2000)
Non-Cart Files in Shopping Cart Folder (1997)
Formatting date to number - more (2000)
(1997)
How To question on setting up downloads (1997)
WebCat and WebTV (1997)
flushdatabases (1997)
Smart caching problems with 2.1b3? (1997)
Country & Ship-to address & other fields ? (1997)