Support

Once again I'm discovering that the "developer.lametric.com" site has become slow and un-responsive.  I'm not going to pretend that I know all your infrastructure, or how or why it happens, but I have some ideas...

I reported the issue months ago about how my Lametric units are constantly doing DNS lookups for this domain, as in several times per second, seemingly because there is no DNS cache or content cache on the units themselves.  So I can surmise that since there are many more LaMetric units out in the world today, they are all effectively creating a DDoS attack on either the DNS host or the webserver of "developer.lametric.com"

I also notice that my browser becomes slow or un-responsive after several minutes of being in the create new icon thing under the create new app, online at developer.lametric.com - to the point that the fan on my PC ramps up wildly.  Clearly, some script or element on the page is having a fit and caught in a loop or some sort.

Today, I first discovered the problem because icons wouldn't display on any messages I send, then I come to discover that's because every icon is loaded from developer.lametric.com, which is currently down, if not terribly slow to respond.

I really wish someone at LaMetric would just accept the fact that this un-necessary cloud dependency (on loading everything from developer.lametric.com) is really a bad idea.  Are there plans to load balance, or dedicate more bandwidth this site, or at least implement caching on the LaMetric device itself?  I'll now need to abandon what I was trying to develop tonight until another day when I find that developer.lametric.com is functioning again :-(

Hi,

2 years after your post, no change, site is still terribly slow :(

Br,JM

I’ve experienced the slowdown in my browser too, especially when I’m in the "create new app" section. 

I have the same problem with developer.lametric.com. The heavy dependence on the cloud is causing development to be interrupted. Hopefully LaMetric can improve the infrastructure or add caching on the device to reduce the load.

You can try using Local API to reduce the dependence on the cloud while waiting for a long-term solution.