1 / 28

Knowing Your Limits

Knowing Your Limits. Jason Fish Informatics @ jasondfish #bweb11. Who should be here?. Designer Developer Administer a website Own a sites content Market a site Manage someone who does the above Use the internet. @ jasondfish. What am I going to tell you?. Mixable

ivory
Télécharger la présentation

Knowing Your Limits

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Knowing Your Limits Jason Fish Informatics @jasondfish #bweb11

  2. Who should be here? • Designer • Developer • Administer a website • Own a sites content • Market a site • Manage someone who does the above • Use the internet @jasondfish

  3. What am I going to tell you? • Mixable • What problem we faced • How we found a solution • What we fixed • Give you in tools to do the same @jasondfish

  4. www.purdue.edu/mixable @jasondfish

  5. What technology did we use? • ASP.NET MVC 2.0 • SQL Server 2008 R2 • Memcached • jQuery • API • Facebook • Twitter • Dropbox @jasondfish

  6. What problem did we face? ? • External content • Images • Videos • Profile pictures • Web service calls • Get student courses • Get faculty courses • Get Facebook data @jasondfish

  7. What could we do? • What would you do? • Cache queries • Just-in-time loading of data • Push processing to the user @jasondfish

  8. Was that enough, or right? • No baseline • No idea on content • Did we focus on the wrong things? @jasondfish

  9. Again, what could we do? • Load Test • process of putting demand on a system or device and measuring its response. • en.wikipedia.org/wiki/Load_test @jasondfish

  10. How do we do that here? • Load Runner • Licensing • Huge learning curve • Intensely time consuming • Why do we have it then? • Blackboard • Banner @jasondfish

  11. Well now what? • LoadStorm • General Electric • Wall Street Journal • Nokia • Woot • Free for 25 users • Very little learning curve • No per user license fee @jasondfish

  12. So how does it work? @jasondfish

  13. Build the Test – The Setup @jasondfish

  14. Build the Test – The Scenario @jasondfish

  15. Run the test within 5 minutes @jasondfish

  16. Yay charts! @jasondfish

  17. Yay numbers! • Key Points • Average Response Time • Errors • Peak Requests Per Second @jasondfish

  18. Final Charts @jasondfish

  19. What’s going on here? @jasondfish

  20. There’s More! @jasondfish

  21. Mixable Results @jasondfish

  22. Mixable Charts @jasondfish

  23. Mixable Charts @jasondfish

  24. Mixable Charts @jasondfish

  25. Why such a big change? • Implement Caching • Queries • Images • Utilize CDN’s • jQuery • Image thumbnailing • Code Optimization • C# • Queries @jasondfish

  26. What else do I need to know? • Servers need to be validated • Admins should be notified • Web Server • Database Server • Only Run on Dev/QA @jasondfish

  27. So, why are you here? • Give you access to LoadStorm for FREE • Email me at jfish@purdue.edu @jasondfish

  28. Session surveys http://www.itap.purdue.edu/boilerweb/survey

More Related