1. What’s Coming? What are we Planning?

2. http://chtc.cs.wisc.edu chtc@cs.wisc.edu › Better docs › Goldilocks – This slot size is just right › Storage › New Hardware What’s next for CHTC

3. http://chtc.cs.wisc.edu chtc@cs.wisc.edu › Why?  Because the CHTC web site sucks. › How?  Improved web documentation on what resources we actually have, how to get started and how to use our tools, like for Matlab and R. › When?  Starting now and continuing until we’re done! Better Documentation

4. http://chtc.cs.wisc.edu chtc@cs.wisc.edu › Why?  We never have the right mix of small vs. big vs. whole machine slots. › How?  Condor enhancements let us ‘watch’ the job queue and re-arrange our slots to best fit queued jobs.  You’ll need to specify in your submit file how many cores, memory, disk, etc. your job needs. Documented now in Condor 7.7.5. Will be documented on CHTC Web site. › When?  Beta: March 5  Production: March 23 Dynamic Slots

5. http://chtc.cs.wisc.edu chtc@cs.wisc.edu › Why?  We’re getting requests from researchers for large amount of storage for processing. › How?  We are deploying a Hadoop Filesystem.  We are adding ‘edge’ connectivity so you can read/write data remotely, for example from OSG nodes. › When?  Beta: March 15  Production: May 1 Storage

6. http://chtc.cs.wisc.edu chtc@cs.wisc.edu › GPUs  We have two GPU systems you can test with today (8 core, 16GB RAM, 896 NVIDIA Telsa M2050 cores)  In partnership with Icecube, we are hosting their GTX9000 GPU cluster (288 CPU cores, 21k NVIDIA Tesla M2070 cores, 1,152 GB RAM, Infiniband) that you may use opportunistically. Expected availability is May 1. › Big Memory  No immediate plans to purchase, but…  Dynamic slots will help  We can also use the IceCube cluster to opportunistically validate your large memory code and go from there › Low latency networking, MPI-capable nodes  No ‘owned’ resources, but we do have partnerships with groups who do have such machines that we can introduce you to, like the IceCube GTX- 9000. New Hardware