
April 8th, 2011, 08:53 AM
|
|
|
|
Yea 5000 is probably exaggeration :P I know that with Google Maps it takes around 0.1 second per request, which isn't too bad.. At this stage im just trying to work out which technology to use, if we can host it ourselves.
The idea is to have a diary open, each event has an address linked to it. When a user tries to create a new event we tell the user how long it will take them to travel between the previous event and the one they're booking in.. this will give them an overview of when to book in the event.
I'm also hoping to run a program that can do the same thing over multiple days, i.e. 50 events per day, 10 days thats 500 events. That would mean 500 directions calculations. I guess if we average 0.5 seconds per calculation running 5 processors (as rough example) then it will take 50 seconds.
We could use this sort of calculation to calculate the cost of running each of these queries.
|