topic Re: too many init.js requests in ArcGIS JavaScript Maps SDK Questions

too many init.js requests

Yue_Zhou — Mon, 21 Nov 2022 18:08:49 GMT

One of my colleagues at performance testing team observed 80 requests for init.js with his 80 CPU core machine. I see 8 requests of init.js calls since my machine has 4 CPU cores. Browser can handle only 6 requests at a time. Hence other key requests are stalled because of too many requests.

Re: too many init.js requests

AndyGup — Mon, 28 Nov 2022 17:20:09 GMT

Hi @Yue_Zhou can you provide more information on your use case for needing that many CPU cores? That's definitely a non-standard hardware configuration for a single web browser user. 80 cores would be more typical for a server-side implementation, or a host VDI machine with dozens or hundreds of users.

In the meantime, thanks for reporting, we'll take a look at the top limit.

Re: too many init.js requests

YueZhou1 — Mon, 28 Nov 2022 22:24:44 GMT

Hi Andy,

Thanks for your response. Yes. I agree with you that 80 core CPU machine is an extreme scenario. However, we are expecting: 1) Init.js/dojo-lite.js files should be loaded only once irrespective of CPU cores. 2) This file is always loaded from server. It should be loaded from cache(from the 2nd time).

Re: too many init.js requests

AndyGup — Fri, 09 Dec 2022 16:30:38 GMT

@YueZhou1what you are seeing with init.js is the API spinning up multiple workers. I can see how that would give the impression there is a caching problem. We ran tests and the API worker initialization caching is working correctly. If you are still having issues, the next steps would be to open a tech support ticket, or call your account representative to meet with a solutions engineer.