As of April 12th, you must go to Progress SupportLink to create new support cases or to access existing cases. Please, bookmark the SupportLink URL and use the new portal to contact the support team.
Carlos,
Just to confirm, you are not getting any error. You are just seeing a delay. Right?
Thanks,
Pranav
Pranav,
Yes, it is just a delay in response time, no error.
1. The name of the collection is "History".
2. The collection has 14 columns.
3. The timestamp is the largest data in any column. ("2017-11-01T00:00:00.000Z" for example).
4. I tried with a simple query (?query={"status":"occupied"}) and it stills takes about 10 seconds to respond.
5. No, this is my largest collection, the other ones that I have are not larger than 100 rows.
6. I have tried Chrome, Firefox, nodejs from Windows console and Postman. All with the same results.
Thanks,
Carlos.
Thanks,
Pranav
BACK-3003
Pranav,
1. The slowdowns are observed at any time that I try to get the query.
2. No, they are not any collection hooks.
3. We have tried in different networks and it takes the same amount of time, about 10 seconds is the fastest response time that we get.
Thanks,
Carlos.
Carlos Fabeiro
Hello,
I have a collection with around 50,000 registers. When I execute a query, either via an Endpoint or REST API that it is supposed to return around 30,000 registers. It tooks around 15-30 seconds. Is this normal or is there anything I can do to speed things up?
The query to the collection is something like this: {"status":"occupied","company":"ABC Co.", "timeend": { $gte: "2017-01-01T00:00:00.000Z", $lte: "2017-11-01T00:00:00.000Z" }}
Thank you.