Update taking an hour!

Neulsaem

Over and over again

We are Korean users and sometimes we update the Proclaim app on a Saturday evening (Korean time)

The update size is only about 100MB but why would it take so long?

FYI, our internet is really fast. So it's not really our internet speed problem.

We were guessing that maybe it is the time your server is most used or something?

When we update the app on a Sunday morning, it's super fast - about a minute or so.

We would really like it to be fixed! Thanks

Find more posts tagged with

Comments

Scott Alexander

Neulsaem, sorry to hear this. The files are coming from Amazon's CloudFront CDN so I don't think load would be the issue. Amazon has servers in Korea so our files should be coming to you directly from that location. I wonder if you're usually the first person to get a Proclaim update from that particular geographic region/server and are paying a penalty as the content is initially cached. An interesting experiment would be to try and install or update Proclaim on a different computer once you've already experienced a slow update. If it's fast on successive updates (same version of Proclaim) then we'll have a good idea what the issue is.

Neulsaem

https://community.logos.com/discussion/comment/883307#Comment_883307

What you said is a spot-on!

We used a desktop to start a download and started another PC to update.

Both took a long time, but once the desktop finished its download, the laptop's update became really fast. So I think your theory is true.

So it's probable that we often were the first folks to download the update?

Is there a solution to this?

This is a serious issue because we often prepare our services in the Saturday evenings,

and, if the update takes an hour, we can't go to bed as early as we should to...

Any thoughts?

Scott Alexander

https://community.logos.com/discussion/comment/883309#Comment_883309

So it's probable that we often were the first folks to download the update?

In that geographic location, yes, at least that's my theory and it sounds like your experience corroborates.

Is there a solution to this?

We may be able to have Amazon "warm up" the cache when we ship a new version. I'll do some research on this next week and follow up. Waiting an hour to do an update (which we do frequently [:)]) is not acceptable. I think we can find a solution.

Neulsaem

https://community.logos.com/discussion/comment/883311#Comment_883311

The "warming up" idea sounds great.
That seems likely to work.

We'll be looking forward to a solution!

Scott Alexander

https://community.logos.com/discussion/comment/883313#Comment_883313

Update: We haven't forgot about this. The current plan is to move to a different CDN which has better support for this scenario.

Neulsaem

https://community.logos.com/discussion/comment/893552#Comment_893552

How is the plan going, if I may ask? ^^

It's still taking an hour!

Scott Alexander

https://community.logos.com/discussion/comment/909695#Comment_909695

How is the plan going, if I may ask? ^^

It's still taking an hour!

Sorry Neulsaem, it's still on our backlog, but we haven't forgotten! [:)]