-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Performance Tests and Benchmarking #103
Comments
Our most typical use-case: Our tables have longitudes and latitudes in columns First, we create an index on
to find all the entries in sometable which have points inside the user-specified circle centered at (1.2345,6.7890) with a radius of 0.166667 degrees. For test data, any large public domain astronomical catalog would work. I'm not sure which ones are public domain though. |
I'm not sure, but I think it is? It says the index is being used. If I add a column to the table named Here's the output of
Partial list of indexes we have on this table:
If I repeat the above, they are much faster on subsequent attempts (or maybe the database was busy doing something else when I tried the first time):
|
Dear Sirs,
There is a suggestion to implement performance tests and benchmark pgSphere. One of the important pgSphere features is the fast access and search to spherical objects using indexes. To improve existing functionality, we need a way to identify bottlenecks and compare modification results. We should benefit from performance testing.
There are some but not all the questions related to performance testing:
- Which data patterns to use?
- Where to get test data?
- How to configure PostgreSQL?
I would like to start discussion of the pgSphere performance testing. I welcome any feedback and suggestions on the subject.
The text was updated successfully, but these errors were encountered: