Hi, IMO we can send a timeout with the operation which, once the operation/ notification is received by the device, it waits for the given timeout and respond back to the server to perform the operation. All operations are sent to devices at ones and the timeout should be different to each device. So that each device gets its own time to contact the server and complete the operation.
Also, this can be used for batch processing as well. As an example, if there are 1000 devices, for first 100 devices, the timeout will be 0s, for next 100, 10s and so on. Then the first batch will come to the server just after they received the operation and the next batch will wait for 10s(or any given time) to respond back. This will reduce the overhead of waiting for a set of devices to complete the operation. I think through this we can limit the number of devices which contact the server at a given time and handle a reasonable amount. Appreciate any feedback. Thanks and regards, Menaka On Mon, Feb 27, 2017 at 11:09 PM, Geeth Munasinghe <ge...@wso2.com> wrote: > Hi all, > > We have encountered an issue with balancing load distribution of device + > server communication. Device and server communication happens through > following ways. > > 1. Polling - Device keeps polling the server > 2. Push notification - Server sends a notification to device to come > retrieve the operation. (wake up call) > 3. Push message - Whole message is pushed to device as notification. > > In 1 and 2 ways, device always comes to server to pick up the operation. > (In MDM scenarios, we use only 1 and 2) We have found few scenarios where > this would lead to a request overload to the server. > > 1. Device information retrieval > 2. Device application list retrieval > 3. Device location retrieval > 4. Policy monitoring > 5. Installing/Uninstalling application (Role based) > > First four scenarios are handled by background tasks. These tasks are > responsible for adding an operation against each of the device. This > process would notify the device regarding operation or device will come to > server at a pre-configured time to retrieve the operation. Specially with > the notification process, when an operation is added to all the device, > notification is send to all of them. In iOS, we send to the notification to > APNS, for android - GCM/FCM and for Windows - WNS. These notification > services normally deliver the messages to devices quickly. Therefore as > soon as device receives the notification, it starts to contact the server. > If this happens with a server which has 1,000s of devices enrolled, most of > devices start retrieving the operation from the server which leads to a > request a burst. 5th scenario happens when we install an application to a > role which has 1,000s of users. This also starts sending notifications to > all the devices of those users, which would result in a request burst. > > As a solution, we can limit the number of devices notified at given > moment. Only set of devices will receive the notification at first, then > after some time interval second set of devices will receive the > notification and continue until all the devices are notified. This way, we > can make sure only chunk of devices receives the notification, hence reduce > the server load. > > Please give your feedbacks and suggestions. > > Thanks > Geeth > > -- > > *G. K. S. Munasinghe* > *Senior Software Engineer,* > *WSO2, Inc. http://wso2.com <http://wso2.com/> * > *lean.enterprise.middleware.* > > email: ge...@wso2.com > phone:(+94) 777911226 <+94%2077%20791%201226> > > <http://wso2.com/signature> > -- *Menaka Jayawardena* *Software Engineer - WSO2 Inc* *Tel : 071 350 5470* *LinkedIn: https://lk.linkedin.com/in/menakajayawardena <https://lk.linkedin.com/in/menakajayawardena>* *Blog: https://menakamadushanka.wordpress.com/ <https://menakamadushanka.wordpress.com/>*
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
