CODEWITHSUNDEEP
meteor
Mehmet Erdoğan
Mehmet Erdoğan

Reputation: 33

Meteor.logout() and Meteor.call() too slow

I have a web app. I am living a problem about time of Meteor.logout() and Meteor.call(). When i meteor.logout(), it takes time between about 30-40 sec. Same for Meteor.call() as well. About 200-250 clients use this system on the same time.

if a client see about 100-200 items his on app screen this delay time is so much. but 10-20 items, it's a little well. we get data every 5-10 sec as different times each others on these items. I mean, live screen.

I don't get this problem when i work this system on diffrent port with same code and same database by the way just use only me.

I can't figure it. What can be reason it. I need your ideas and help.

Upvotes: 0

Views: 657

Answers (4)

Mehmet Erdoğan
Mehmet Erdoğan

Reputation: 33

I solved my problem.

While the collection update process is performed from one side, the meteor publish process is performed from the other side. As the number of clients increases, the server becomes unresponsive. I solved it with Mongodb oplog feature.

Thank you for your interest.

Upvotes: 1

Vinay Chaudhary
Vinay Chaudhary

Reputation: 318

You can use this.unblock() in every method and publications. By default, Meteor process requests one by one, it will queue all the requests coming, if one is processing.

This may be due to the reason that some of the functions doing some bigger functionalities will be requiring more time and all other request to the server have to wait till it ends.

You need to simply place this.unblock() at the starting of every method and publications and it will not block your requests. Thanks

Upvotes: 1

Faiz Mohamed Haneef
Faiz Mohamed Haneef

Reputation: 3596

There could be multiple reasons. There could be unsubscription of collections, which means client and server exchange the list of id's which are being unsubscribed.

You many have reactive UI, which suddenly gets overwhelmed with the amount of data that is being transferred and needs to update itself. (example angular digest cycle always runs after meteor sub/unsub)

Chrome Inspector - Network websocket frame is your best tool understand how soon Meteor logout fires and and if there are any messages being passed back and forth before server retutns the result of logout request.

You may also use this.unblock() feature in subscribe. This way your subscritption run parallelly and don't block each other

Upvotes: 0

Okei
Okei

Reputation: 127

The logout function waits for a callback form the server, there is something wrong with the way you have configured your server.

Run the same code on another machine, it should not happen.

Upvotes: 1

Related Questions