Consuming too much memory and CPU resources when sending push to large number of users about laravel-fcm HOT 8 CLOSED

Ok thank you very much for your investigations. I'm currently working on a queue implementation. It should be available soon

Best Regards

from laravel-fcm.

Any idea of a time frame for the queue implementation?

Also would be great if you could have a notification channel implementation ( Similar to https://github.com/benwilkins/laravel-fcm-notification ). I could send a pull request and get this working if you already have the queue implementation somewhere. Please let me know

from laravel-fcm.

@brozot I've been looking into your code and it seemed to be written correctly and doing fine by sending a single request in chunks. But because it is a sync. call and it was making system pretty slow during the process so another option for me was to move this task to a background process. As this package doesn't work out of the box with Laravel Jobs/Queues as mentioned here so I've to come up with some other way around. I ended up writing my own code to communicate with FCM servers and moved that to a background job, that seemed to be working pretty good and also not stopping the normal flow of application. Although it is taking almost same amount of resources as your code does, so still thumbs up to your work and it really helped me getting around this situation.

from laravel-fcm.

Hi, The package should work well for this amount of token. Group and Topics is a different usage. I will take a look.

Maybe can you share your log file ?

Thank you very much

from laravel-fcm.

@brozot thanks for responding. I really don't have logs for threads and all that I got this information from support guy. He was synced with me when this process was going to trigger. But I do have some usage screen shots may be they can clarify how much impact it had on the system.
Before and after usage:

When push was being sent;

And this thing caused a huge slow down on our APIs and as well on our cPanel.

from laravel-fcm.

@brozot anything on this issue?? Or can you suggest me any alternate implementation?

from laravel-fcm.

It's quite strange because the package should have send only one http request to FCM.

Maybe you can check that you make only one call (storage/logs/laravel-fcm).

All your tokens are valid ?
There are a loop in the response if there are a failure. But i will be surprised if this loop has a bad influence with your server, maybe can you log a timestamp before and after it.

from laravel-fcm.

@tahirwaseer Have you find something wrong ?

from laravel-fcm.