Re: [WebDNA] WebDNA code validator

This WebDNA talk-list message is from

2011


It keeps the original formatting.
numero = 107153
interpreted = N
texte = > Our site search does search a lot of fields and may be the source of = our problem. Site search certainly increases as traffic increases. site search should be extremely fast, but for instance if you try to = match every single entry from a database against another database, the = number of operations involved can be counted in hundred of thousand if = not millions. > For instance, if you use [append] against a large database, it will = rewrite the entire database to disk after each single [append]." >=20 > What would be considered a large database? (Our largest is 57MB) Yes, 57MB is a pretty large database. Not for WebDNA, for your disk. A = good 7200rpm or 10.000rpm dik will need one or two seconds to write = this. If you have a lot of disk I/O at the same time, this might produce = a latency that would be significant. This is why WebDNA 7.0 writes to = RAM. You can also change [append] for [replace] as suggested by Govinda = few weeks ago on this list: things will go much faster. - chris= Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] WebDNA code validator (Kenneth Grome 2011)
  2. Re: [WebDNA] WebDNA code validator (christophe.billiottet@webdna.us 2011)
  3. Re: [WebDNA] WebDNA code validator (Donovan Brooke 2011)
  4. Re: [WebDNA] WebDNA code validator (Donovan Brooke 2011)
  5. Re: [WebDNA] WebDNA code validator (Daniel Meola 2011)
  6. Re: [WebDNA] WebDNA code validator (Daniel Meola 2011)
  7. Re: [WebDNA] WebDNA code validator (christophe.billiottet@webdna.us 2011)
  8. Re: [WebDNA] WebDNA code validator (Donovan Brooke 2011)
  9. Re: [WebDNA] WebDNA code validator (Daniel Meola 2011)
  10. Re: [WebDNA] WebDNA code validator (Donovan Brooke 2011)
  11. Re: [WebDNA] WebDNA code validator (Donovan Brooke 2011)
  12. [WebDNA] WebDNA code validator (Daniel Meola 2011)
> Our site search does search a lot of fields and may be the source of = our problem. Site search certainly increases as traffic increases. site search should be extremely fast, but for instance if you try to = match every single entry from a database against another database, the = number of operations involved can be counted in hundred of thousand if = not millions. > For instance, if you use [append] against a large database, it will = rewrite the entire database to disk after each single [append]." >=20 > What would be considered a large database? (Our largest is 57MB) Yes, 57MB is a pretty large database. Not for WebDNA, for your disk. A = good 7200rpm or 10.000rpm dik will need one or two seconds to write = this. If you have a lot of disk I/O at the same time, this might produce = a latency that would be significant. This is why WebDNA 7.0 writes to = RAM. You can also change [append] for [replace] as suggested by Govinda = few weeks ago on this list: things will go much faster. - 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:

WebCat2b13MacPlugIn - More limits on [include] (1997) Apoligy (1997) Accepting credit cards (1997) any suggestions for creating a multi-lingual site? (1999) SSL, WebSTAR, WebCatalog (1998) test (2000) [BULK] Fwd: [WebDNA] [BULK] WebDNA discovery in the Console - [having many crashes] (2011) ShowNext (1997) browser info.txt and SSL (1997) i'm dumb today (2004) mac hack (1997) Modify Database (1998) Search with Special Chars (1997) international time (1997) Emailer setup (1997) Web Delivery Page concept (1997) OT: WebDNA and LINUX (2004) WebCatalog 2.1b3 - Plugin or cgi ? (1997) default value from Lookup (was Grant, please help me) (1997) [SearchString] usage (1997)