> > what is the upper bound for interrupt latency? If we have an inner loop, > without calls, I would assume we could have a reasonable number of > instructions and iterations before that latency would be adversely affected? >
Yes, interrupting doesn't need to be immediate. There are situations where users can observe the latency of interrupting a long-running loop, so it should be something that a human perceives as fast. To give numbers, I'd aim for no more than 10ms latency on fast hardware, so that it won't be more than 100ms on slow hardware. If an order of magnitude less than this upper bound can be achieved without significant drawbacks, that's even better. -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/v8-dev/CAKSzg3Rj%2Bk8GwTsECE-mRDWweU5g_kAHm1QV2_K%3DBkjmf4zAUQ%40mail.gmail.com.
