- Nov 01, 2014
-
-
zzz authored
Fix history.txt UTF-8 breakage Javadoc fixes after review
-
- Oct 31, 2014
- Oct 30, 2014
- Oct 26, 2014
-
-
zzz authored
-
- Oct 24, 2014
-
-
zzz authored
-
- Oct 23, 2014
- Oct 20, 2014
-
-
zzz authored
Switch back to QueuedThreadPool (ticket #1395) In Jetty 5/6, the default QTP was not concurrent, so we switched to ThreadPoolExecutor with a fixed-size queue, a set maxThreads, and a RejectedExecutionPolicy of CallerRuns. Unfortunately, CallerRuns causes lockups in Jetty NIO. In addition, no flavor of TPE gives us what QTP does: - TPE direct handoff (which we were using) never queues. This doesn't provide any burst management when maxThreads is reached. CallerRuns was an attempt to work around that. - TPE unbounded queue does not adjust the number of threads. This doesn't provide automatic resource management. - TPE bounded queue does not add threads until the queue is full. This doesn't provide good responsiveness to even small bursts. QTP adds threads as soon as the queue is non-empty. QTP as of Jetty 7 uses concurrent. QTP unbounded queue is the default in Jetty. So switch back to QTP with a bounded queue, which does what we want, which is first expand the thread pool, then start queueing, then reject. ref: http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/ThreadPoolExecutor.html https://wiki.eclipse.org/Jetty/Howto/High_Load
-
- Oct 18, 2014
-
-
zzz authored
-
- Oct 17, 2014
-
-
zzz authored
-
- Oct 16, 2014
- Oct 15, 2014
-
-
zzz authored
-
- Oct 14, 2014
- Oct 13, 2014
- Oct 10, 2014
- Oct 08, 2014
-
-
zzz authored
-
- Oct 07, 2014
- Oct 05, 2014
-
-
zzz authored
- Remove duplicate load3 and load4 methods - Change load3 return type to int - Comment out dead stores - Re-roll the add, subtract, and negate loops; there's no speed benefit or timing reason to unroll them - Check for field already set - Remove shifts by 0
-
- Oct 04, 2014
-
-
zzz authored
-