Re: How reliable is WebDNA?
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 58660
interpreted = N
texte = We run Washington state's Vote.WA.Gov election reporting system using=20WebDNA and the county reporting system, VoteWashington.org - have been=20=since 1998. On election night we receive about a million hits between=20=8:00 pm and midnight; 12 million hits in the first week following an=20election.Because of the political nature of the system, down down - even a=20minute or so - is simply not an option. We have had exceptional=20results with WEBDNA.The issue sounds more a matter of data design and data modeling - doing=20=dynamic sites involves certain disciplines that take time to learn. If=20=you are using databases, planning your data model is more important=20than writing the code. Since you are not a "programmer", you need to=20either learn this side or work with someone who can assist you.I couldn't design a straight line with a ruler, but we use freelance=20designers to help build the foundation from which we work. We have no=20=employees, so use strategic relationships with other key disciplines to=20=fill in where we do not have the expertise. I suggest you consider=20some of these options.LarryOn Jun 27, 2004, at 3:43 PM, Cristi=E1n Tapia wrote:> Hi all,>> I've been a fan of WebDNA since year 2000. I'm not a programmer, I'm a> designer, but thanks to WebDNA I've been able to design powerful and> intelligent websites that I never thought I could create.>> Nevertheless, because of my experience with the product in the last=20> months> now I'm considering using amother solution for database and dynamic> content management. To be honest I don't want to do it, I don't want =to> start learning another programming language and I don't want to =rebuild> all the WebDNA sites I've developed, but my clients are complaining=20> and I> don't want to loose my business because of this.>> The problem is that every time the WebDNA engine is (as I consider)=20=> under> "pressure", it can't handle the situation. Some databases can't be=20> opened,> some pages aren't found, and I get this error on my system.log:>> Jun 25 15:06:56 xserve WebDNA[22819]: Could not establish connection=20=> with> the module.>> Server statistics for a busy day are:>> 200.000 page views> 7.000 unique visitors> 300 concurrent visitors (max).> 1.500.000 hits> 8 GB transferred> 120 databases for 45 sites>> I would like to know if this scenario is too much for WebDNA, or if =the> problem can be platform, processor or RAM related.>> I'm using WebDNA 5.1 on an Xserve 1.2 Ghz with 512 MB of RAM.>> Any hint, comment or advice would be greatly appreciated. I'm willing=20=> to> get some answers, tips or anything that can be helpful from other=20> WebDNA> users from the list.>> Thanks a lot.> Regards,> ---------------------------------------------------> Cristi=E1n Tapia Smith> Lim=F3n Creativo Internet y Multimedios> ctapia@lemongroup.cl> http://www.lemongroup.cl> Fono: 562-3468600>>>> -------------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list
.> To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to=20> > Web Archive of this list is at: http://webdna.smithmicro.com/>>Larry Hewitt360.807.1100 =OFFICEHCO, LLC360.807.1103 =FAX1133 Kresky NE #106360.508.6231 CELLCentralia, WA 98531larryh@hewittco.comwww.hewittco.com=www.votewashington.org-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
We run Washington state's Vote.WA.Gov election reporting system using=20WebDNA and the county reporting system, VoteWashington.org - have been=20=since 1998. On election night we receive about a million hits between=20=8:00 pm and midnight; 12 million hits in the first week following an=20election.Because of the political nature of the system, down down - even a=20minute or so - is simply not an option. We have had exceptional=20results with WEBDNA.The issue sounds more a matter of data design and data modeling - doing=20=dynamic sites involves certain disciplines that take time to learn. If=20=you are using databases, planning your data model is more important=20than writing the code. Since you are not a "programmer", you need to=20either learn this side or work with someone who can assist you.I couldn't design a straight line with a ruler, but we use freelance=20designers to help build the foundation from which we work. We have no=20=employees, so use strategic relationships with other key disciplines to=20=fill in where we do not have the expertise. I suggest you consider=20some of these options.LarryOn Jun 27, 2004, at 3:43 PM, Cristi=E1n Tapia wrote:> Hi all,>> I've been a fan of WebDNA since year 2000. I'm not a programmer, I'm a> designer, but thanks to WebDNA I've been able to design powerful and> intelligent websites that I never thought I could create.>> Nevertheless, because of my experience with the product in the last=20> months> now I'm considering using amother solution for database and dynamic> content management. To be honest I don't want to do it, I don't want =to> start learning another programming language and I don't want to =rebuild> all the WebDNA sites I've developed, but my clients are complaining=20> and I> don't want to loose my business because of this.>> The problem is that every time the WebDNA engine is (as I consider)=20=> under> "pressure", it can't handle the situation. Some databases can't be=20> opened,> some pages aren't found, and I get this error on my system.log:>> Jun 25 15:06:56 xserve WebDNA[22819]: Could not establish connection=20=> with> the module.>> Server statistics for a busy day are:>> 200.000 page views> 7.000 unique visitors> 300 concurrent visitors (max).> 1.500.000 hits> 8 GB transferred> 120 databases for 45 sites>> I would like to know if this scenario is too much for WebDNA, or if =the> problem can be platform, processor or RAM related.>> I'm using WebDNA 5.1 on an Xserve 1.2 Ghz with 512 MB of RAM.>> Any hint, comment or advice would be greatly appreciated. I'm willing=20=> to> get some answers, tips or anything that can be helpful from other=20> WebDNA> users from the list.>> Thanks a lot.> Regards,> ---------------------------------------------------> Cristi=E1n Tapia Smith> Lim=F3n Creativo Internet y Multimedios> ctapia@lemongroup.cl> http://www.lemongroup.cl> Fono: 562-3468600>>>> -------------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list .> To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to=20> > Web Archive of this list is at: http://webdna.smithmicro.com/>>Larry Hewitt360.807.1100 =OFFICEHCO, LLC360.807.1103 =FAX1133 Kresky NE #106360.508.6231 CELLCentralia, WA 98531larryh@hewittco.comwww.hewittco.com=www.votewashington.org-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Larry Hewitt
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] divisible by 1 (2011)
Two submit buttons ? (1997)
RE: Still Learning (1997)
ETA on Dreamweaver extensions? (2000)
[/application] error? (1997)
Bug? (1997)
hideif/showif causes error if wrapped around searches (2003)
Browser Reloads and AddlineItem (1997)
Nested Loops and SHOWIFs (1997)
Calendar using WebCatalog? (1997)
[SearchString] usage (1997)
RequiredFields template (1997)
Nav4 not specifying cart (1997)
cart file creation (2003)
Includeform Error (2002)
Setting user and password (1999)
WebCat2.0 [format thousands .0f] no go (1997)
Include a big block of text (1997)
Buying sans cart (1997)
WC2.0 Memory Requirements (1997)