Re: [BULK] Re: [WebDNA] abstraction code can be tricky...

This WebDNA talk-list message is from

2012


It keeps the original formatting.
numero = 108313
interpreted = N
texte = >> webdna's allotted ram-usage limit for lack of a better term, I called it that ("webdna's allotted = ram-usage limit"). Let me explain: Obviously the company line is that the only limit is the amount of RAM = on the server machine. But coding aggressively has for some/many of us revealed a phenomena - = that a page which tries to use "more RAM than what we usually gobble up = with our code", can, when hit with the browser, simply never load in the = browser.. and even if we then comment out (or delete) the offending code = (note: *properly-sytaxed*, but just RAM-hungry code), then upon reload = in the browser, Webdna keeps serving up an old copy of the file.. a copy = which no longer exists on disk. And all this while webdna caching is = turned OFF in the admin interface. I KNOW others beside myself have = seen this. And I am not talking about a page that tries to use all 6GB = of RAM that is sitting idle/available... (or so one would reasonably = think).. but just code that pushes the limit just a little too far. Sound too fuzzy? Sure; it is hard to quantify, and describe, since I = can't see under the webdna engine hood to know exactly what is = happening. I tried to make my last post useful but just saying, effectively, "Hey, = in case your page never loads, and your webdna cache seems to be stuck = (for that page), then see if you are defining and calling a function = within another function." HTH -Govinda= Associated Messages, from the most recent to the oldest:

    
>> webdna's allotted ram-usage limit for lack of a better term, I called it that ("webdna's allotted = ram-usage limit"). Let me explain: Obviously the company line is that the only limit is the amount of RAM = on the server machine. But coding aggressively has for some/many of us revealed a phenomena - = that a page which tries to use "more RAM than what we usually gobble up = with our code", can, when hit with the browser, simply never load in the = browser.. and even if we then comment out (or delete) the offending code = (note: *properly-sytaxed*, but just RAM-hungry code), then upon reload = in the browser, Webdna keeps serving up an old copy of the file.. a copy = which no longer exists on disk. And all this while webdna caching is = turned OFF in the admin interface. I KNOW others beside myself have = seen this. And I am not talking about a page that tries to use all 6GB = of RAM that is sitting idle/available... (or so one would reasonably = think).. but just code that pushes the limit just a little too far. Sound too fuzzy? Sure; it is hard to quantify, and describe, since I = can't see under the webdna engine hood to know exactly what is = happening. I tried to make my last post useful but just saying, effectively, "Hey, = in case your page never loads, and your webdna cache seems to be stuck = (for that page), then see if you are defining and calling a function = within another function." HTH -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:

WebCat2b12 - nesting [tags] (1997) Deleting Orders (1997) [WebDNA] backup / mirror website & databases (2018) Summing fields (1997) [ModDate] & [ModTime] ? (1997) E-Mailer (WebCatb15acgiMac) (1997) Signal Raised (1997) could someone please try this - it's very quick and easy (2000) ANYONE (1999) emailer on Windows Beta 18 (1997) [Webcat 2]Next (1997) Multiple prices (1997) Bug Report, maybe (1997) What am I missing (1997) RequiredFields template (1997) SmithMicro FTP problems (2002) AddLineItem Problem (1997) seeminly simple... but beyond my grasp :) (2000) Cart doesn't interpret tag! (1997) checkbox results written to a database (1999)