Jump to content

System Response


HxRoamer

Recommended Posts

I have bitten my tongue and kept quiet on this issue for a long time, but tonight I just have to say that the system response when logging finds at weekends in appalling.

 

We have had a wonderful day out during which we found 65 caches. Nice to get home, pour a gin and tonic, and then start logging.

 

I have been at the computer 2½ hours and have managed to log just 12 finds. Most of the time is just waiting for the system to respond. I have also had to re-enter four of the logs again as I got an "Internet Explorer cannot display the web page" message after pressing the 'Submit' key and the log was lost.

 

At this rate it is going to take me 12 hours to log my finds - longer than it took us to actually find them!

 

Come on Groundspeak. I pay my premium membership and that should allow me to log my caches on the day I find them.

Link to comment

Unfortunately I have to agree with HxRoamer on this, since changing maps on the website to mapquest the response time is awful. I wait for the map to load, then wait for it open a quick view of a cache, if I zoom in it won't load at all!! I don't know what has happened but PLEASE change it back, it is very frustrating to continually wait for the page to load. As a premium member I expect a better experience, I love caching but not logging my finds or doing a quick search for a new cache to find without doing a pocket query. Thankyou for trying to improve the website but currently it sucks please fix.

Link to comment

I doubt mapping has anything to do with it. Today is Saturday, and Groundspeak may be experiencing a unsual volume of traffic to the site, or there is an issue with a Server or other underlying problem. If this is the case, please be patient, and either let the bandwidth open up, or let the Groundspeak crew take care of any issues.

Edited by GeoLobo
Link to comment

Sorry for the inconvenience but are you still seeing the slowness ?

 

Sorry for not responding last night nkroy. It was getting late in the UK so after posting this message I turned off my computer and went to bed. All back to normal this morning.

 

I hope that GS will urgently address this problem, particularly at weekends.

Link to comment

It still takes literally ages to log a find in the early evening hours (CEST).

 

Firefox Web Console log:

 

[18:14:53.360] GET http://www.geocaching.com/js/jquery_plugins/jquery.countable.js [HTTP/1.1 200 OK 130328ms]

[18:17:03.676] missing ) after condition @ http://www.geocaching.com/js/jquery_plugins/jquery.countable.js:63

[18:17:04.075] GET http://ads.Groundspeak.com/a.aspx?ZoneID=9&Task=Get&SiteID=1&X=%2706a40f967aed46c6b5e6b874fc86575a%27 [HTTP/1.1 200 OK 578ms]

 

Kind regards

Link to comment

Domo!!!

 

Is the site down, or having a problem now?

Status page says nothing bad, but I cannot access anywhere Geocaching except for this forum.

Weird.

 

Tried Safari & Firefox on Mac OS 10.6.8.

No go.

 

What going on?

 

Im getting a runtime error, its been pretty poor performance for some weeks on and off, particularly bad on Sundays. Like back to the good old days again.

Mark

Link to comment

Here I am again one month after my last post and once again I am having to wait minutes for pages to download. This is not acceptable.

 

Two things spring to mind. Firstly, when the system is busy premium members should get priority over non-premium members. Secondly, geocaching is growing at an almost exponential rate. You only have to look at the number of caches being published (and thanks to our volunteer reviewers for all their hard work). I assume that the number of premium members is growing at a similar rate - hence Groundspeaks revenue is growing at a similar rate. How about investing in additional computer capacity?

 

It is getting to the point that we dread getting home after an enjoyable day's caching for fear as to how long it is going to take to log our finds.

 

Come on Groundspeak - please do something about it.

Link to comment

Domo again.

 

"Runtime Error" message I just got, trying to access my profile.

 

http://www.geocaching.com/error/error.aspx?aspxerrorpath=/my/default.aspx

 

----

 

Server Error in '/' Application.

 

Runtime Error

 

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

 

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

 

<!-- Web.Config Configuration File -->

 

<configuration>

<system.web>

<customErrors mode="Off"/>

</system.web>

</configuration>

 

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

 

<!-- Web.Config Configuration File -->

 

<configuration>

<system.web>

<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>

</system.web>

</configuration>

Link to comment
I have also had to re-enter four of the logs again as I got an "Internet Explorer cannot display the web page" message after pressing the 'Submit' key and the log was lost.

As an aside, I believe Firefox doesn't throw away the text in this case; you just hit Back and it'll still be there. (I believe; there are so many versions to keep track of.)

 

One other thing I've gotten in the habit of: After I've entered a long log, I'll Select All then Copy (via right clicks), thereby keeping a temporary backup copy in my computer's clipboard.

Link to comment

Interesting that the site is still very slow today and some of the pages are not loading or loading with minimal data - status says all OK?

AFAIK, that page isn't automatically updated. Someone at Groundspeak has to go in and manually change the page. That's almost worse than not having it at all.

Link to comment

Interesting that the site is still very slow today and some of the pages are not loading or loading with minimal data - status says all OK?

AFAIK, that page isn't automatically updated. Someone at Groundspeak has to go in and manually change the page. That's almost worse than not having it at all.

They kind of need to put in a "Site Response speed:" indicator on the status page (auto updated) so that we at least can tell if the issue is on our end or at Groundspeak's.

Link to comment

Interesting that the site is still very slow today and some of the pages are not loading or loading with minimal data - status says all OK?

AFAIK, that page isn't automatically updated. Someone at Groundspeak has to go in and manually change the page. That's almost worse than not having it at all.

They kind of need to put in a "Site Response speed:" indicator on the status page (auto updated) so that we at least can tell if the issue is on our end or at Groundspeak's.

 

Agreed.... never knew there was a status page.....!!

 

We need an auto update script as manual does not work anymore... we live in an "on demand" culture :anitongue:

Link to comment

AFAIK, that page isn't automatically updated. Someone at Groundspeak has to go in and manually change the page. That's almost worse than not having it at all.

They kind of need to put in a "Site Response speed:" indicator on the status page (auto updated) so that we at least can tell if the issue is on our end or at Groundspeak's.

 

Agreed.... never knew there was a status page.....!!

 

We need an auto update script as manual does not work anymore... we live in an "on demand" culture :anitongue:

The site is down, but the status page tells that everything is working! The status is useless :(

Link to comment

I'm still experiencing extreme page load times in the evening hours (CEST). Good old http (no SSL):

 

[20:20:43.605] GET http://www.geocaching.com/images/wpttypes/sm/3.gif [HTTP/1.1 304 Not Modified 312ms]

[20:22:56.807] missing name after . operator @ http://www.geocaching.com/js/jquery_plugins/jquery.countable.js:63

[20:22:57.078] GET http://www.geocaching.com/images/logo_print_bw.png [HTTP/1.1 304 Not Modified 484ms]

 

Kind regards

Link to comment

I'm still experiencing extreme page load times in the evening hours (CEST). Good old http (no SSL):

 

[20:20:43.605] GET http://www.geocaching.com/images/wpttypes/sm/3.gif [HTTP/1.1 304 Not Modified 312ms]

[20:22:56.807] missing name after . operator @ http://www.geocaching.com/js/jquery_plugins/jquery.countable.js:63

[20:22:57.078] GET http://www.geocaching.com/images/logo_print_bw.png [HTTP/1.1 304 Not Modified 484ms]

 

Kind regards

I'm not sure I'd classify less than half a second as "extreme". The time you mentioned in your earlier post of 130 seconds is what I would agree is extreme.

 

The early evening hours for you is mid-morning for me. I'm having no problems at all with loading times, no matter the time of day. The only times I ever see slow page loading is on some Sundays, and even then it's only a few seconds longer than usual. You might want to try clearing your cache, checking your add-ons, etc. to see if the problem is local to your computer. If the site were consistently this bad for everyone, I would think there would be more than a single topic with an average of a post a day on these forums.

Link to comment

I'm still experiencing extreme page load times in the evening hours (CEST). Good old http (no SSL):

 

[20:20:43.605] GET http://www.geocaching.com/images/wpttypes/sm/3.gif [HTTP/1.1 304 Not Modified 312ms]

[20:22:56.807] missing name after . operator @ http://www.geocaching.com/js/jquery_plugins/jquery.countable.js:63

[20:22:57.078] GET http://www.geocaching.com/images/logo_print_bw.png [HTTP/1.1 304 Not Modified 484ms]

I'm not sure I'd classify less than half a second as "extreme". The time you mentioned in your earlier post of 130 seconds is what I would agree is extreme.

Half a second? Have a look at the time code in brackets at the beginning of the log lines. There are 2 minutes, 13 seconds between the first two entries and that qualifies for "extreme" even in your terms :-)

 

The log shows three consecutive lines from Firefox's web console trying to load log.aspx.

 

Comparing the log I posted on April 22nd and the log above shows that the problem might be related to jquery.countable.js. Did someone familiar with JavaScript have a look at that?

 

Kind regards

Link to comment

Half a second? Have a look at the time code in brackets at the beginning of the log lines. There are 2 minutes, 13 seconds between the first two entries and that qualifies for "extreme" even in your terms :-)

Whoops, sorry. I was just looking at the time in milliseconds at the end of each line. I never thought to compare the timestamps. In that case, I'd agree with you that it's extreme, but I still maintain that it is most likely a problem on your end. What happens if you try to go to that Javascript URL on its own? I just tried it, and it came up instantly. Have you tried clearing your cache, in case your browser has cached a corrupted version of that file?

Link to comment

but I still maintain that it is most likely a problem on your end. What happens if you try to go to that Javascript URL on its own? I just tried it, and it came up instantly. Have you tried clearing your cache, in case your browser has cached a corrupted version of that file?

Me any many others (according to social networks discussing the issue) have that problem. Of course I cleared the Cache, reloaded the page, tried IE 11, FF 11, FF12. If the feedback forum would still exist, it would be obvious that there is a problem. Most users don't know about this forum and the users that know don't use it because anything they write here will be linked to forever from their profile.

 

Loading the JavaScript URL on it's own doesn't make any sense, because the code won't execute then.

 

Kind regards

Link to comment

Most users don't know about this forum and the users that know don't use it because anything they write here will be linked to forever from their profile.

:blink: Why should anyone care whether their posts are linked to forever from their profile? Pretty much anywhere I post anything on the Interwebs, once I post it, it's there forever, and search engines will show the posts.

 

--Larry

 

Edited for minor grammar error.

Edited by larryc43230
Link to comment

Here I am on a Wednesday evening trying to log my finds. Taking at least 45 seconds to get a response and then more often than not is says "Casche is Unpublished" - can't be, I have found it.

 

I can accespt that the traffic is very high at a weekend (though the system should be able to cope with it) but I find it hard to understand why it is so slow mid-week.

 

I think there was an update last night. Could this have made things worse?

 

This terrible response is taking much of the fun out of geocaching. Please Groundspeak get it fixed once and for all.

Link to comment

We had some server updates last night that could be the source of this slowdown. Our IT team is investigating at the moment.

 

Appears to have been fixed in the last few minutes as I am suddenly getting them posted almost instantly.

 

Thank You

Edited by PhilatSea
Link to comment

We had some server updates last night that could be the source of this slowdown. Our IT team is investigating at the moment.

 

Appears to have been fixed in the last few minutes as I am suddenly getting them posted almost instantly.

 

Thank You

 

Not resolved here. Just now, it took 30 seconds to open my profile page (I tried twice in a row... 30 seconds each time)

Link to comment

 

Not resolved here. Just now, it took 30 seconds to open my profile page (I tried twice in a row... 30 seconds each time)

 

Geocaching.com is horribly slow to load here too. Seems to have just started last night though.

Link to comment

We had some server updates last night that could be the source of this slowdown. Our IT team is investigating at the moment.

 

Appears to have been fixed in the last few minutes as I am suddenly getting them posted almost instantly.

 

Thank You

 

Not resolved here. Just now, it took 30 seconds to open my profile page (I tried twice in a row... 30 seconds each time)

Not fixed here, either.

 

Just clicked on the spyglass on the front page (to see all caches near me) and waited and waited. Nothing. Came over here to post and checked back. Still trying to load. Just now (2+ minutes later), it came back but not with my local cache list--instead, it's got a secondary search ("All Geocaches") with my coordinates loaded. It's as though the front page doesn't trust my coordinates and asks me again... 2 minutes later.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...