Talk:BaDTunes
CS290F Fall 2006 - UCSB Computer Science - Thorsten von Eicken
Project Comments
Looks good guys. The data models are well thought out. There a few small things: for example, you probably want the ratings table to simply refernce the users table (who wrote the review/rating), and also the musics table. The rating and review can simply be data fields in this table. But this seems close enough that I suspect you'll figure all of that out when you get to it.
You may also want some more controllers. Typically, your controllers correspond to the major data models and provide CRUD functionality for those, maintaining the ancillary data objects as a side effect.
Finally, and I've been saying this a lot, but you need some transactional functionality. I'm not sure what that would be, but it's not obvious from the current description.
Stefan 15:29, 27 October 2006 (PDT)
- Neat site! Brett's gonna have to sing for the demo...
- Looks like you're not getting the hang of Rails URLs or the OO dispatch, bummer.
- Re: "NOTE: Apparently adding index only helps when select query used with exect matches...", the problem is that the string indexes are string prefixes (you specify the length of the prefix when creating the index) and you are searching for %blah%. It should use the index if you searched for blah% (prefix search). Not great from a UI point of view, but good enough for testing scalability in the class...
- Excellent SQL analysis: nicely presented too.
- Are you guys up for a demo on monday? (Not sure this is a question, really :-)
TvE 23:45, 17 November 2006 (PST)
- Nice presentation of the performance results!
- I don't understand your arguments to httperf. It seems you set the rate way too high and the total number of sessions too low. The benchmark should run ~30 seconds to get repeatable results. You should set --rate to values roughly between 0.2 and 10.
- The graphs all say that your optimizations reduce the performance. Mis-labeled?
- The graph titles do not correspond with the Y axis.
- How big is your database (rows/bytes)?
- What is the rate of real Rails page requests per second (ignoring static & image requests)?
- You state that the DB is the bottleneck: how do you know?
- Assuming you understand where the bottleneck is, you next step should probably be to break the server into two: one for mysql and the other for apache+rails. Now the fun really starts!
TvE 23:56, 28 November 2006 (PST)
