ok thanks, i was pretty sure it is "normal behavior" i am only
asking if there is away around that particular behavior, and your
answer was what i figured might be the case.......
so i am a little clearer, it is normal for apps to use disk IO in
the way we are describing, even if there is no real memory pressure,
correct? (a form of it's virtualization?)
I am looking at "cacheing" right now to see if there could be anything
better done in that area. in IB , i disabled everything for the
webView.... (java, java script, ect...)
the program is not relaunching every 20 secs, it is reloading a
webView every 20 secs. and then doing a bunch of work on that
data, there is no real calls to anything API except of course the
webView reload itself, which i assume is what is causing normal
memory use, it definitely is causing a CPU use spike, and there is no
user interface to update, except again, for the webView object
instance, and it is hidden... there is only number crunching
after the webview load... including using memory to store
variables...
i never thought there was anything wrong, only maybe a way to keep
the process from using disk swaps as it's source of memory.
Jon.
On Oct 10, 2009, at 11:03 AM, Bill Bumgarner wrote:
In other words: No, there isn't a way for your app to use "real
memory". Or, to rephrase
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
