Where did the sticky threads go?

[[Diplomacy] Carnegie]

As the title.

I guess they're the new ADS.

 

[Xious]

Maybe it's a server issue...

 

[Lightspeed]

The glue has a shelf life .... it didn't quite make it to 2019.

 

[Stealthie]

"Working as intended"

 

[rootsrat]

As the title.

I guess they're the new ADS.

As far as I'm aware Brett is doing some maintenance on the forums, so maybe that's the reason. But I'll let him know about this thread, maybe there is an issue.

 

[Brett C]

Don't mind me, throwing hammers at the forums currently.

 

[Brett C]

Still working on the forums.

Turned them back on for the time being, there may be some slowness while some caches and such are being rebuilt.

 

[Brett C]

Maintenance finished for the night/morning.

Caches will be slow to rebound after the SQL Server upgrade that happened.

If you're logged out, this is why.

 

[Brett C]

One thing is for sure, viewing threads feels quite fast now... but forumdisplay.php is that thorn in my foot.

 

[Bravada Cadelanne]

I'm guessing forumdisplay is doing a query that is difficult to create indexes for?

 

[Brett C]

I'm guessing forumdisplay is doing a query that is difficult to create indexes for?

Close but not quite.... IN (0,1,2) on thread visibility. Not sure how aware you are with SQL, but IN () generally translates to IN 0 OR 1 OR 2, which can be extremely slow with larger boards.

 

[Patrick_68000]

As the title.

I guess they're the new ADS.

They will come back for 2019.

Happy new year !

 

[Riverside]

Thanks Brett, much more the slicker for putting my words into now

 

[Wizz15]

Perhaps a query like <=2 would work better?

Assuming there are no negative numbers you want to exclude

 

[Nick Sticks]

What's Brett done wrong?
Working on the forums on the night shift

 

[The Lawful]

Close but not quite.... IN (0,1,2) on thread visibility. Not sure how aware you are with SQL, but IN () generally translates to IN 0 OR 1 OR 2, which can be extremely slow with larger boards.

Depends on the execution plan optimizer, and how it internally translates the syntax. In Oracle or MSSQL, IN queries with fixed values are lightning fast. The traditional approach would be something like 'AND t_visibility >= 0 AND t_visibility <= 2' and may actually be faster here, as you have to deal with a sequence of values and only need to check the boundaries.

O7,
[noob]

Still locked out completely for 48+ hours because of the Cavalieri bug. Ticket #00000242455. Won the Tier 10 Festive Level in World of Tanks in the meantime, but that's no substitute. Hey, I prolonged my holidays by 3 days just for ED and now I just sit there. Fate is cruel.

 

[The Lawful]

Perhaps a query like <=2 would work better?

Assuming there are no negative numbers you want to exclude

Yes, that would even be faster, provided that NULL processing is out of the way as well. NULL vs. ZERO is always a possible pitfall. We have a rule internally to never use 0 as a database constant because of this.

O7,
[noob]