The (Slowly) Open Sesame article here provides an honest assessment of using Sesame for real world applications.
Here's an excerpt:
When dynamically generating SPARQL for SESAME - I seemed to have gained .5 second by adding filters to the end of the statement. Is SPARQL executed in SESAME in a way that this would make sense?
See the discussion at : http://www.openrdf.org/forum/mvnforum/viewthread?thread=1430
I'm going to take an application specific approach to solving the problems I'm facing with speed. By application specific, I mean that I will depend on another piece of software in the dependency chain - that being Caucho's Resin fast Java serverlet container. Why? To avoid sending lots of data and doing lots of queries over HTTP.

212 queries to load the front page of AHIRC. That'll do it.
This happens because I am trying to emulate the "COUNT" mixed with "GROUP BY" you'd find in SQL. One company has it:
http://docs.openlinksw.com/virtuoso/rdfsparqlaggregate.html
And looks like others are anxious:
http://simile.mit.edu/mail/ReadMsg?listId=14&msgId=16326
But it's not an easy problem in a broader context:
http://www.ldodds.com/wordtin/Wiki.jsp?page=UniqueNamesAssumption