Home page history

CS290F Fall 2006 - UCSB Computer Science - Thorsten von Eicken

Final Presentations

• Coffee & bagels will be provided!
• Project 4 code turnin: run turnin project.4@sgk <directories & files>. No data please! (My quota's not that high.)
• Have your presentation ready, preferably on the wiki. Please use my laptop to present as we have no time to switch laptops from one group to the next. If you need powerpoint, upload the presentation to the wiki.
• Have your demo ready & running on one instance. Remember how little time you have! You want to give everyone a *flavor* of your site, not a demo of all the features. Awake their curiosity so they check it out later today! Avoid sign-up steps: have an account ready with the data you need for the demo, etc. Focus on a couple of highlights of your project, don't try to present all your results.
• Have your final write-up done before the class in the form of your wiki pages.
• Turn-in your source code.
• Have one final instance running with your application so we can poke at it after the presentations.
• Check the project 4 for details.

News

• ATTENTION POSTGRESQL USERS: there's a new rails image that has the ruby-postgres gem installed instead of the postgres-pr gem. This gem is a C extension that interfaces with the postgres server and may improve your database performance substantially. Give it a try.
  • Note that the ruby-postgres database driver is experimental. While it is faster—if it works—I have run into problems using it. If you encounter inexplicable strange behavior after switching to using this image, this may be the culprit.
• At last, a Deployment to multiple servers capistrano script with instructions. Other than loading the data into your database once it's fired-up, everything is automatic! I don't have an app I can test exactly the version of the script that I posted, so please le me know if you find a problem.
• Plots: be sure to plot replies/sec vs. connections/sec and response time vs. connections/sec. Requests/sec is less interesting. Also, be sure to vary connections/sec so you see all 3 phases: unloaded, ramp-up, maxed-out.
• Please terminate the instances you are not using! It's not OK to leave multiple instances running 24/7. We don't have the budget for that... Thanks.
• Before running tests with more than 3 application servers, please have me review what you have.
• I commented on projects that sent me an email. If you'd like feedback, please sen me an email.
• I added a section on deploying to three machines at the end of the Deployment page. Ports FYI: all TCP ports are open between instances, however, from the outside, only ports 22, 80, 443, 3000, and 8080 are open.
• A new image with memcached is available as CS290f-FC5-v5. A list of all the images is now at EC2 Images and you can check using memcached for some pointers. Stefan Kaes wrote and interesting article about optimizing Rails.
• Deployment: step-by-step instructions on how to deploy your Rails app.
• SVN server out of disk space: we notified CS support, I fear nothing will happen before monday morning :-(.
• Using httperf: some initial tips.
• If you cannot attend the project presentations on Thu Dec 14th, please send me email so I can schedule your demo in class Wed Dec 6th.
• Wei reports an error in the deploy.rb, see the note on the Talk:Deployment page.
• Please terminate your project 3 instance if I have been able to review it (check the discussion page of your project). No point using up our credits now...
• New image available: FC5+apache2.2+rails+mysql5.0 v2, now with s3sync, postgres, and mysql slow query log. Run s3cmd listbuckets to see cs290f buckets & create your own using s3cmd create <bucketname>. For slow mysql queries see /var/lib/mysql/mysql-slow.log and read the mqsql manual entry.
• Final project presentations are tentatively set for Thursday December 14th 9am-11am. This is during our final exam slot. I'm trying to confirm availability of the class room. Please see the project 4 handout for the final project schedule.
• Deployment: a new EC2 image is available together with step-by-step instructions on how to deploy your code to it. Please check it out and comment on the page if something doesn't work.
• Project 3 review: I reviewed all sites with running instances. Please check the discussion page. For many sites I could not get to any web pages, please fix. Overall it looks like we're ready for some fun times trying to make thes sites scale! TvE 00:44, 18 November 2006 (PST)
• The new rails image (v.4) has Apache 2.2.3 installed under /usr/local/apache2.
  • IMPORTANT: it seems the C bindings for ruby-mysql are missing in this image. If you're getting errors about /tmp/mysql.lock try installing the mysql gem as follows:
    gem install mysql -- --with-mysql-include=/usr/include/mysql --with-mysql-lib=/usr/lib/mysql
    apologies for not catching this earlier.
• Want to connect to your database instance directly? Here's how to do it using an SSH tunnel.
• AWS How-to guide for setting up a rails image and getting your application running on it.
• All of you should have received an invitiation to the AWS Console for managing EC2 servers. If you have not, please send me email.
• Deployment with capistrano info.
• Example Mephisto deployment script that installs mephisto on a fresh EC2 "cs290f rails" image.
• Project 3 handout finalized.