New Calguns Is Terrible

[okdo]

Super slow and searching takes forever. Thought this was supposed to be better??????

[9Cal_OC]

It’s your internet

[theleafybug]

When it first went live I logged in instantly, I was zipping around like crazy - some of the fastest loading pages I've ever seen. A few hours later and now I can barely log in after the 5th try, takes forever to load. Not sure what the problem is if it's the server performance or bots or ddos or something, but it's bad right now.

[sacmer]

I have also been having the same problem all day and no, it is not my home internet. Speed is unchanged and every other website/browsing working as normal.

[jsclimbs]

Lighting fast at 6 AM PST

[ACfixer]

Really hit/miss. Super fast right now.

EDIT: Right after I posted that it locked up and it took me until now to get back. 23 minutes of failure.

[Kyle1886]

Really hit/miss. Super fast right now.

EDIT: Right after I posted that it locked up and it took me until now to get back. 23 minutes of failure.

Same here, yesterday and the day before the site was almost unusable.

I'm here for the long haul though.

Kyle

[lemans]

You gotta do your thing early in the am. Later it gets bogged down, but still useable. Just wait a few minutes.

[Kyle1886]

Generally time of the day makes little difference. I've not been able to get in at 0230 hrs or any time between then and 0600 hrs. At times I can got on but not go anywhere with a "WORKING" message or the ole 504 Gateway boot.

I don't know the cause but the number of folks on at that time a few, including guests.

As I type now I'm getting that "WORKING" message doing nothing but type.

Internally something is "scheduled" to activate. I had similar issue with an anti-virus which was no longer supported. Every 24 minutes it scanned the "Security-SPP part of the system and bogged things down.

Kyle

[tradecraft]

Unusable

[RudyN]

It is a mess right now. There is no way that I can find on deleting all of the posts that I do not want to read. It was easy to use before it was "improived" I hope that it can be fixed as I really liked being o here.

[SniPeralez]

Ay Caramba!😒

[choochoo]

LOL, I thought I was the only one having issues here.

[bluesky762]

worse than the last version of the original before the upgrade

[command_liner]

It is hard to get a complete view on what is wrong. There are serious bugs in the HTML generation -- you can use the Chrome developer tools to find dozens.
These bugs generate uncaught exceptions that generate timeouts. These break the time-continuity of the page draw, which makes for 503 and 504 errors.
There are resource problems somewhere -- as I mentioned elsewhere -- because the overall time to get some things done is off by a factor of a million or so.

Earlier observations about bad compression still apply, but are not the main issues. There are LOTS of problems in the industry with poor implementations of
multi-threaded zstd. Like the reference Python implementation has been wrong a few times, which caused chaos. Cloudflair has screwed this up repeatedly
for many customers, but the basic rule applies. This site should send only zstd-compressed data.

Something like 25 years ago I wrote the first *correct* multi-threaded zlib package, and it had (IIRC) 26 boundary conditions that needed correct thread
control. The zstd problem is quite a bit harder, so I have some sympathy. But they should have been able to get it right in the last 6 years. It is not *that*
hard.