Are the numbers the same for both FF and Chrome? Chrome may just have better optimization for workers. Chrome may have discovered that sharing between multiple processes is better than multi-threading for Workers.
I'm not an expert on Workers and multi-threading, but I always thought that there is little advantage, and potential a disadvantage, of running more threads of equal priority than there is CPU/Core availability. FF is known for having overhead from other FF plugins. The difference in performance you are seeing could be from that as well. HTH, -Alex On 2/4/14 8:02 AM, "Marcus Fritze" <marcus.fri...@googlemail.com> wrote: >Thanks for the quick response. > >Activity Monitor shows mostly 175 - 185 % and sometimes a max of 196 %. > >But my overall CPU usage is about 22%. > >Am 04.02.2014 um 16:51 schrieb Alex Harui <aha...@adobe.com>: > >> What does the os tools show for cpu usage? Maybe FF doesn't spread work >> to more than one or two cores. >> >> -Alex >> >> On 2/4/14 7:38 AM, "Marcus Fritze" <marcus.fri...@googlemail.com> wrote: >> >>> Hi, >>> >>> Ok, I have a main application and a worker. >>> >>> The worker is for very CPU intensive work. But I have a lot of "work" >>>to >>> do at the same time. >>> So I run multiple worker (actually the same Worker-class) at the same >>> time. >>> >>> In Chrome everything is working fine and the work is done in some >>>seconds. >>> Chrome starts a "Google Chrome Helper" process for every worker. >>> >>> But In Firefox, it seems there is only one "Firefox Plugin Process" and >>> when I have 3 or 4 worker >>> at the same time, the main app slows down. >>> >>> Any suggestions? >>> >>> Info: my system Mac OS X 10.9 and the latest Firefox and Flash Player >>>12 >>> >>> Thanks >>> >>> Marcus Fritze >> >
