Re: CPU Creating Objects vs Modifying Object Properties
- From: Joost Diepenmaat <joost@xxxxxxxxx>
- Date: Thu, 31 Jan 2008 22:04:04 +0100
dhtml <dhtmlkitchen@xxxxxxxxx> writes:
I'm still wondering about how to measure CPU for double threads.
Double threading will result in nearly double the amount of processing
being done in the allotted time. For a time-based animation, this
would mean nearly twice as many frames. If little system memory is
available, then the program should not hog two threads.
WHat are the pros/cons of using two setIntervals?
Pros:
1) double workload
COns:
1) can make animations jerky in MOzilla
I need to make a decision: Should I use 1 or two threads?
I don't know what you mean. No Javascript implementation I know uses
multi-threading, but appears you mean something else...
Joost.
.
- References:
- CPU Creating Objects vs Modifying Object Properties
- From: dhtml
- Re: CPU Creating Objects vs Modifying Object Properties
- From: GArlington
- Re: CPU Creating Objects vs Modifying Object Properties
- From: dhtml
- CPU Creating Objects vs Modifying Object Properties
- Prev by Date: Re: ISO a taxonomy of AJAX errors
- Next by Date: Re: CPU Creating Objects vs Modifying Object Properties
- Previous by thread: Re: CPU Creating Objects vs Modifying Object Properties
- Next by thread: Re: CPU Creating Objects vs Modifying Object Properties
- Index(es):