search

saulogt / test-parse-server4

0 stars 0 forks source link

Performance Issues on 4.x #1

Open dplewis opened 3 years ago

dplewis commented 3 years ago

@saulogt Thank you for the Testing Repo, it helped out. I tried it on my MBP 16 (we may have different specs) with direct access on the schema-reduction branch which I made that reduces schema calls on object creation.

Created 300 accounts in parallel through cloud function (Installation + User + Account) accounts: 4102.379ms Created 1500 myObjects in parallel objectsP: 592.556ms Created 1500 myObjects in sequence objectsS: 786.885ms

I've actually never though about doing

await Promise.all([Parse.Cloud.run(), Parse.Cloud.run(), ... (298x Parse.Cloud.run()]);

Since the error you got is already fixed on the master branch I can try to look into 4.5.0

saulogt commented 3 years ago

It looks very promising Thanks for taking some time to test that

It a shame that Parse Server release cycle is so lagging. I'd love to see this and many more improvements deployed

saulogt commented 2 years ago

Hey @dplewis! I know it's a very long time ago you opened it... I just tested the last version (4.10.4) and I still see those errors below. Have you noticed them?

[Error]
error: Uncaught internal server error. {"stack":"Error"}

The beta version (5-beta4) on the other hand seems fine in this test. Cheers!