[webkit-dev] strategy for evaluating performance issues related to memory.

[Mike Marchywka]

________________________________
> From: jorlow at chromium.org
> Date: Mon, 21 Jun 2010 18:22:19 +0100
> Subject: Re: [webkit-dev] strategy for evaluating performance issues related to memory.
> To: marchywka at hotmail.com
> CC: webkit-dev at lists.webkit.org
>
> On Mon, Jun 21, 2010 at 2:21 PM, Mike Marchywka> wrote:
>
>
>
>
>
>
> So where does this stand right now? I hope to actually contribute at some point.
>
> but right now I'm just trying to determine approaches to even finding the problems.
>
> ( and yes my disk light still comes on for minutes at a time locking me out of doing antyhing
>
> with iceweasel or firefox)
>
> Yes, you've mentioned your disk light blinking several times now. If you have specific bugs to file against specific projects, I suggest you do that. Repeatedly posting about it on webkit-dev (until now, in unrelated threads) doesn't seem particularly useful.


I honestly think this has become a very big problem in many cases and no one seems to appreciate it.
It is simply meant to motivate the rest of the post. 


>
>
>
>
> I guess at a gross level it would be nice to know when and why page faults occur
>
> but a more pro-active approach would be to start understanding the memory
>
> needs during design or code examination for other reasons. If there is nothing
>
> better, perhaps people could put in formatted comments about memory needs
>
> and access patterns and various parameters or issues or assumptions that
>
> in the code. I haven't entirely thought this through (duh) and hope to stimulate
>
> a discussion ( actually I'd be happy if someone had a one line answer or link
>
> to an answer but am not that opitmistic).
>
>
>
> I would approach this as an addition to finding memory leaks but maybe the
>
> worst offenders will go away if there is less clutter.
>
> This is all fairly hand-wavy. If you have specific problems you've seen, please file bugs. If you want to spend some time investigating these issues, great. But I don't understand why you keep bringing this up. Especially since, as far as I can tell, it only involves situations where WebKit memory is spilling to virtual memory which, AFAIK, is not something anyone has spent time optimizing.


This list has discussed many topics relating to bugs, coding conventions, performance, features, etc. These
are not independent issues- presumably coding relates to ease of debug and optimization etc.
I'm trying to put together a strategy for digging into the memory issues which everyone seems to agree have
been largely ignored. Long before VM becomes a problem, usually you have cache problems so I wouldn't
say that is the only issue but certainly the most noticable when it happens. 
Given that no one seems to have looked at it, it is reasonable for me to be concerned that there
won't be many obvious clues in the code. If people are more aware of the possible problems
perhaps they could leave comments related to memory usage in various places, as just
one hand-waving thought. 

If I find a bunch of stuff like  "new Widget[x]" what am I suppoed to think about it without knowing
where "x" comes from ?


>
>
>
> Unless you're actively working on this problem within WebKit, these emails seem out of scope for webkit-dev.

The topic addresses this doesn't it? I would think that outlining a development strategy would be "actively working."
I don't expect to dig into the code right now beyond what I have already done but if I could figure out
what to do I might be able to make more specific contributions later. 

>
>
>
>
> Thanks.
>
>
>
>
>
> - - - - - -
>
>
>
> Mike Marchywka | V.P. Technology
>
>
>
> 415-264-8477
>
> marchywka at phluant.com
>
>
>
> Online Advertising and Analytics for Mobile
>
> http://www.phluant.com
>
>
>
>
>
>
>
>
>
>
>
> note new address
>
> Mike Marchywka
>
> 1975 Village Round
>
> Marietta GA 30064
>
> 415-264-8477 (w)<- use this
>
> 404-788-1216 (C)<- leave message
>
> 989-348-4796 (P)<- emergency only
>
> marchywka at hotmail.com
>
> Note: If I am asking for free stuff, I normally use for hobby/non-profit
>
> information but may use in investment forums, public and private.
>
> Please indicate any concerns if applicable.
>
>
>
>
>
>
>
>
>
> _________________________________________________________________
>
> Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox.
>
> http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_1
>
>
>
> _______________________________________________
>
> webkit-dev mailing list
>
> webkit-dev at lists.webkit.org
>
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>
>
 		 	   		  
_________________________________________________________________
The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail.
http://www.windowslive.com/campaign/thenewbusy?tile=multiaccount&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4