0

We have a collection that contains about 30K entities. When we query for a subset using a UUID of another entity in another collection there is quite a delay (5-10secs on avg.). Is there a way to optimize this? Would creating connections be faster? We are assessing APIGEE as a potential back-end for millions of entities so this is a huge problem for us. Any recommendations would be appreciated!

Cheers

MoreScratch
  • 2,933
  • 6
  • 34
  • 65

1 Answers1

0

Using connections is much more efficient (generally) than using queries. With queries, it is the number of search terms that can be a problem, not the number of entities in the collection. Large collection sizes shouldn't really impact performance. Please share an example query if you can - maybe we can help optimize?

Also, we are just putting the finishing touches on a major upgrade that will significantly improve performance of the API BaaS product. Ask your contact at Apigee for more info.

One last thing to consider is that our developer offering may not have the same performance as our paid products. Apigee strives to offer awesome performance on developer, but because of the architecture and SLAs of our paid offering, we can definitely cater to your needs to make sure you have the performance required.

rockerston
  • 521
  • 2
  • 10
  • We were sorting on a date property. After removing the sort (moving it to client instead) performance is excellent. We will look at connections as well. Many thanks. – MoreScratch Sep 11 '14 at 22:56