Ian Bambury wrote:
> Well, 1000 clubs with 10 courts and 24/365 and one booking means 1 booking
> record in a traditional SQL database. It's hard to see how this is really
> horribly-inefficient when compared to checking 100 million records to find
> the one used booking if I do it the way some people are suggesting here.
The GAE engine solution will find the unbooked courts in a single
index lookup. It will never scan the index nor will it ever scan 100
million records as you suggest. It will perform the same whether
there is just 1 booking or there are 50 million bookings. If your SQL
based solution requires the database to scan indexes then finding an
unbooked court amongst 50 million bookings would be much slower than
doing search with just 1 booking.
You should probably ask on some SQL DBA forum whether your SQL based
solution will scale on the database engine you would expect to use.
Both performance of queries and contention during updates will need to
be considered. If it does scale well then you've got a compelling
argument against using GAE, who's biggest avantage is scalabilty. If
it doesn't scale then you still may be able to find an alternative SQL
based solution that does, even if it means writing some of your own,
efficient, code.
Ross Ridge
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---
