Re: [WebDNA] Serial numbers and pricing for WebDNA 7.0
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106112
interpreted = N
texte = One problem we found (with the help of Ken Grome) with WebDNA is that = [append] was automatically and systematically writing to disk, whatever = the preference settings. Imagine a GB busy database with one append = every minute: the huge file will be written to disk every single minute. = In this case, writing speed will be related to disk I/O speed. We decided to directly write to RAM and heavily test the new behaviour = in the particular case where the RAM database starts at let's say 400K = and jumps to 10MB: WebDNA RAM allocated space has to grow accordingly. = It works but it may crash in some specific cases, for instance when the = RAM limit is reached (for instance, for WebHosting providers with = RAM-limited VPS). The solution we use in WebDNA 7.0 is an automatic "security" disk flush = when 1000 records have been appended. Otherwise, the preference settings = allows to flush to disk after each [append] if the old behaviour is = prefered. - chris On Jan 22, 2011, at 14:09, Govinda wrote: > 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)
Associated Messages, from the most recent to the oldest:
One problem we found (with the help of Ken Grome) with WebDNA is that =
[append] was automatically and systematically writing to disk, whatever = the preference settings. Imagine a GB busy database with one append = every minute: the huge file will be written to disk every single minute. = In this case, writing speed will be related to disk I/O speed. We decided to directly write to RAM and heavily test the new behaviour = in the particular case where the RAM database starts at let's say 400K = and jumps to 10MB: WebDNA RAM allocated space has to grow accordingly. = It works but it may crash in some specific cases, for instance when the = RAM limit is reached (for instance, for WebHosting providers with = RAM-limited VPS). The solution we use in WebDNA 7.0 is an automatic "security" disk flush = when 1000 records have been appended. Otherwise, the preference settings = allows to flush to disk after each
[append] if the old behaviour is = prefered. - chris On Jan 22, 2011, at 14:09, Govinda wrote: > 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)
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:
SKU lookup (1997)
requiring form fields? (2000)
Cart # Starting at 1000 (2000)
grouping fields (1999)
[movefile] (1999)
Banner Ad example (Typhoon) and WebCatalog (1997)
Moving files from one server to another... (2001)
Help with Shipping Costs (1997)
Changing price for a SLU based on options (size, etc.) (1997)
OK, here goes... (1997)
WebCatalog/Mac 2.1b2 - PIXO (1997)
RequiredFields template (1997)
Formatting (2000)
Bug with periods in [math] variable names (2001)
Sendmail - Attachment / My First Post (2001)
[isfile] ? (1997)
More Applescript (1997)
Still having math problems (1997)
Moment of Thanks (1997)
No luck with taxes (1997)