|
|
Post by newuser on Jan 9, 2019 10:04:45 GMT
I recently upgraded to v6.1 (from about 5.5? can't remember exactly) and since then some database interactions are taking a lot longer.
The only model that has become slow has about 13 data items on it, and it's only slow if it returns more than 1 record.
The more records stored against this model the slower it's getting at searching, is there any known issues or reasons this might be happening?
|
|
|
|
Post by Vladimir Musulainen on Jan 9, 2019 10:24:12 GMT
What platform? Android, iOS? Please look into this ticket. is there something in common? |
|
|
|
Post by newuser on Jan 9, 2019 11:19:49 GMT
I've had a look and it's not really related to that. This is happening on all platforms, iOS, Android (and Mac when I'm debugging).
There's over 5000 records for this model (and each one has 13 properties), I'm doing a search for about 20 of these and it's taking about 4+ seconds.
I tested not putting any conditions on it and it just hung in the debugger, so it's not faster doing it that way like the ticket suggests.
|
|
|
|
Post by Super Admin on Jan 9, 2019 11:24:28 GMT
Try to use Fixed Schema instead of property bag
|
|
|
|
Post by newuser on Jan 9, 2019 11:28:42 GMT
Is that the only recommendation?
Is there any explanation for it being instant in previous version and now it's slow?
|
|
|
|
Post by Super Admin on Jan 9, 2019 11:31:43 GMT
If you need urgent explanation and a resolution you should to obtain paid Rho support subscription.
|
|
|
|
Post by newuser on Jan 9, 2019 11:37:33 GMT
It's not urgent, I can wait for an explanation when you have time thanks.
|
|
|
|
Post by Alex Epifanov on Jan 9, 2019 13:24:30 GMT
newuser This is a known regression in PropBag performance related to upgrade of libsqlite. The workaround is to create an index by executing following SQL statement: create index by_object on object_values (object, source_id);
|
|
|
|
Post by fnllc on Feb 15, 2019 15:36:47 GMT
I'm having the same issue with Rhodes 6.1.10. The index is already present apparently because when I try to add it, I get an error saying it already exists.
The performance drop compared do Rhodes 5.5 is very significant.
|
|
