30 May, 2011

1 commit


27 May, 2011

5 commits

  • …from working, however doing so seems to significantly impact max throughput (around 20%), probably due to context switching during Future.get() calls.
    
    #### From OpenDS SDK SVN history for revision 6650 #####
    
    Backout xxxrate threading changes introduced in revision 6648 since they prevent the -M (throughput throttling) option from working. Several attempts were made to fix it:
    
    1) Putting the adaptive sleeps inside the ConnectionWorker.operationComplete callback causes the Grizzly worker thread to be blocked which, in turn, delays other incoming results on other connections (and impacts their etime calculations).
    
    2) Instead of doing adaptive sleeps, I tried putting the "delayed" requests into a ScheduledExecuterService, but this just introduces more complexity (e.g. more threads), more context switches, etc. 
    
    At this point, I decided to go back to the original design.
    
    The new threading strategy introduced in revision 6649 seems to more than compensate for the performance benefits made in revision 6648.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@6935 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@6934 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@6933 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@6932 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@6931 41b1ffd8-f28e-4786-ab96-9950f0a78031
    mark
     

26 May, 2011

6 commits


25 May, 2011

6 commits


24 May, 2011

13 commits


23 May, 2011

9 commits