How things are updating...

[weeds19]

Hey Rocketsciguy,

Have you tried sending BFin a polite email asking her if that was really the cache she meant to log? As a cache owner with a few BC caches, I get logs like this a few times a year. About 75% of the time when I email the logger and politely ask them if they really did do the "10 mile hike with 3000' of gain" they respond and apologize for accidentally logging the cache. Usually it's an honest mistake (careless, but honest).

-Weeds

[bikephotog]

I am one of the two people who have found that cache. It is a major hump with a very steep finish. It took me about 4 hours to complete the round trip. The other finder is my best bud JeoCacher and he said the same. I hate to question anyone's finds as I have been on the other end many times, but this is very surprising. BP

[rocketsciguy]

Weeds, No I probably won't and I'm not sure that I will, unless I start making plans to find that cache. Pointwise, I'm not competitive with her in any category (yet), and it's otherwise not my concern... Just heading out the door this morning, saw the post, and said "What?!" If I were BikePhotog or JeoCacher, though.... Well, I suppose I could do it as a delegate of this community because I've met her once and corresponded cordially a few times, although I think Desert Dawg may know her better....

[Corfman Clan]

As of right now:
The site has 103,270 caches. Of those, 86,113 have been updated. We also have 7,886,816 found logs and 150,004 geocachers.

Unfortunately, not much was happening for close to 11 hours due to a couple of issues I won't delve into here. Things should be better tomorrow.

[Corfman Clan]

As of right now:
The site has 102,972 caches. Of those, 88,839 have been updated. We also have 7,936,980 found logs and 150,425 geocachers.

[Corfman Clan]

As of right now:
The site has 102,599 caches. Of those, 91,838 have been updated. We also have 8,029,416 found logs and 151,090 geocachers.

[Corfman Clan]

As of right now:
The site has 102,242 caches. Of those, 95,140 have been updated. We also have 8,121,932 found logs and 151,747 geocachers.

[Corfman Clan]

As of right now:
The site has 102,106 caches. Of those, 97,412 have been updated. We also have 8,180,340 found logs and 152,379 geocachers.

[Corfman Clan]

As of right now:
The site has 101,873 caches. Of those, 99,620 have been updated. We also have 8,262,720 found logs and 153,151 geocachers.

Getting close!

[Corfman Clan]

As of right now:
The site has 101,170 caches. Of those, 100,617 have been updated. We also have 8,066,949 found logs and 153,758 geocachers.

Only 553 caches left. Hopefully this will finish up tomorrow, though only caches with lots of finds are left so it takes longer to go through them. We can also see that close to 700 archived caches were removed from LonelyCache since yesterday's update along with lots of find logs from them. I'm thinking that a lot of the orignal ET Highway caches may have just been swept away.

[Corfman Clan]

All caches in LonelyCache have now been updated

[rocketsciguy]

All caches in LonelyCache have now been updated

Cool. Nice to get to this point, and to just have to test how well the PQs and data refresh functions keep the site up-to-date. Have been enjoying exploring the beta site, and when I get some time, will have some suggestions (if they haven't already been addressed). Thanks for all your hard work Corfman Clan!

[Corfman Clan]

I just checked to see where the site is at now, since it has been about 3 and a half months since the database was first updated.

As of a couple of minutes ago, the site has 105,959 caches. We also have 8,512,924 found logs and 159,717 geocachers.

Roughly, that's an increase of about 4,700 geocaches, 450,000 found logs, and 6,000 geocachers.

[Corfman Clan]

Since it's a new year, I thought I'd check the counts on the site.

As of right now there are 107,950 caches, 8,706,639 found logs and 161,813 geocachers.

There sure are a lot of caches being hidden and found. It's really sad with all that hiding and finding that there are some caches that haven't been found for years.

[cosninocanines]

A question I have been finding several caches over the last week and seem to be having a problem with them updating on my profile. First only a couple showed up then over the next few days a couple more showed up. Yesterday I found a couple and only one updated. Am I doing something wrong? I went to my profile and checked the update box and renewed my permission to geocaching.com but still the finds are slow in showing up. I'm also having trouble logging on from AOL so that may be part of the problem. Thanks for any help on this.

[Corfman Clan]

A question I have been finding several caches over the last week and seem to be having a problem with them updating on my profile. First only a couple showed up then over the next few days a couple more showed up. Yesterday I found a couple and only one updated. Am I doing something wrong? I went to my profile and checked the update box and renewed my permission to geocaching.com but still the finds are slow in showing up. I'm also having trouble logging on from AOL so that may be part of the problem. Thanks for any help on this.

I believe this is due to the Site Update Issue that has been reported. When stats are being updated, all other updates are suspended. For some reason, the site update is not completing. I believe when we resolve that issue, this should clear up.

[Greybeard-42]

Until a few years, ago, I was a software guy, mainly Modeling and Simulation. It seems that you could run an algorithm before making queries, which would automatically bucket or prioritize which caches to query first. Suggested attributes for the algorithm are the ones you have already chosen: # of visits, last update (days since), age,... to determine which cache's are most likely to change enough to change their "loneliness" value during the next update cycle. Since the oldest ones don't change there value a whole number, but every 3 or 4 days, they don't, necessarily, need to be update every day.

As you run that locally, it could just throw caches into multiple buckets to be queried in order. Technically, as you get the updated information back, you could determine which bucket each cache would fall into for its future update.

Just some thoughts...that you probably already know...

[Corfman Clan]

I believe this is due to the Site Update Issue that has been reported. When stats are being updated, all other updates are suspended. For some reason, the site update is not completing. I believe when we resolve that issue, this should clear up.

The stats update was stopped and won't be attempted again until the regularly scheduled time tomorrow morning at 2:00 AM AZ time so your recent finds should be updated until the stat update process kicks in.

[Corfman Clan]

Until a few years, ago, I was a software guy, mainly Modeling and Simulation. It seems that you could run an algorithm before making queries, which would automatically bucket or prioritize which caches to query first. Suggested attributes for the algorithm are the ones you have already chosen: # of visits, last update (days since), age,... to determine which cache's are most likely to change enough to change their "loneliness" value during the next update cycle. Since the oldest ones don't change there value a whole number, but every 3 or 4 days, they don't, necessarily, need to be update every day.

As you run that locally, it could just throw caches into multiple buckets to be queried in order. Technically, as you get the updated information back, you could determine which bucket each cache would fall into for its future update.

Just some thoughts...that you probably already know...

Hi and welcome to LonelyCache!

Currently updating every cache's score in LonelyCache (as of now, all 108,843) only takes a few seconds so it isn't worth trying to narrow the list and it would probably take more processing time to do so. Today's database systems such as SQL Server, which LonelyCache uses, are very good at optimizing queries, inserts, updates, etc.

The query we're having problems with (an insert from query) is for the Overall Backcountry leader board. In the past, this query as been completing in under 90 seconds, but since Wednesday morning hasn't completed after 30 minutes and is then cancelled because it's taking too long. I'd imagine something changed to cause a minimum 20x increase in processing time. We don't know what that is and will have to work with the web hosting company to figure that out. Maybe they have a sick DB server. Maybe they changed some configuration for something else that inadversely impacted LonelyCache. I really don't know. I hope to hear back from the DB admin tomorrow morning and with some luck, he'll have some ideas on what is going on.

Thank you for your thoughts and ideas. They are appreciated. Again, welcome to LonelyCache

[cosninocanines]

I believe this is due to the Site Update Issue that has been reported. When stats are being updated, all other updates are suspended. For some reason, the site update is not completing. I believe when we resolve that issue, this should clear up.

The stats update was stopped and won't be attempted again until the regularly scheduled time tomorrow morning at 2:00 AM AZ time so your recent finds should be updated until the stat update process kicks in.

Thanks that was it, all the caches updated yesterday.