VBSeo and Multi Page Threads - Problems?

[MarkoP]

Can someone please explain to me the issue with threads with multiple pages?

Is it vbseo that has trouble with them or is it vb itself?

What exactly is happening with multi page threads and can anything be done to stop them from using massive amounts of CPU?

I can't really stop having multi page threads, just closing them down is on the stupid side. A forum is for discussion and a thread might go 50 pages. Some of ours do. I have them set to show 50 posts per page but it's still not helping.

Do I really need to change board platforms because of this?

Thanks!

[briansol]

edit, i read this question wrong.

[Mert Gökçeimam]

Yes , this is actually a vBulletin problem however we implemented a work around for this problem to next version of vBSEO.

[USA Carry]

What exactly is the problem?

[Mert Gökçeimam]

If you allow your users to choose to show different number of posts , the links for posts will not work correctly.

[USA Carry]

I don't think I allow that so I'm fine I guess.

[briansol]

wow, i read this question completely wrong the first time around. Sorry.


Yes, if default option is set to 25 per page
but a user has 30 set,
when you pass a link to /some-thread/page28/
the user who has custom options is going to see an entirely different set of posts that guests and non-altered users will, and vice versa.

[MarkoP]

Hi Brain,

No you got it right the first time. I'm asking about the CPU usage when a thread gets huge. We have threads that run 10 pages or so and I see them coming up in WHM as using up 60% CPU at times.

[Mert Gökçeimam]

In order to solve that you should close threads that reach 1000 post and open a new one. When calling a thread that contains more than 1000 post mysql uses way too much server resources.

[MarkoP]

Hi Mert,

That's what I was trying to find out. So my only options are to close threads? That is really hard to believe. Why on God' earth would they do something like this?

Did they not think some people would have big boards with over 100,000 members?

This has got to be one of the dumbest things I've ever heard of.

[MarkoP]

Mert,

When you said there would be a work around for this in the upcoming vbseo release, was you meaning this problem I'm having with huge threads or the other problem with people seeing different threads or whatever?

I don't have that problem because no one can set different thread views on my forum. The only problem I have is when threads get big.

As far as closing them down and starting another, I don't even see how that could work. I would have to open a new thread using the members account somehow, posting under his name. That would create an admin/mod nightmare. Way too much work.

With this and the adsense stuff they are pulling I'm seriously thinking about finding another board platform.

[Michael Biddle]

IIRC the problem that is fixed in the new version is to link a certain post to the correct page, even if lets say I have 50 posts per page, and you only have 10. If you were to give me the permalink from your post, it would be on page 6, to where mine would be on page 2.

[briansol]

Ok then Yes, Marko, the problem exists in vbulletin itself.

starting around 913 in showthread.php, you can see the building of the post ID string, and then the HUGE query around line 983 which does there WHERE post ID's in (the huge list).

the longer the thread, the long the post ID list.

I personally think a left outer join to thread and a where p.threadid = $threadid would be MUCH more efficient.
Perhaps they had better reasoning for this, i don't know.