CC running slow because I'm doing some software tests

[Shaun]

Apologies for the slowness of CC at the moment. I'm running some import tests on the new software and it's using up a big chunk of the server resources.

Should be back up to speed within an hour or so.

Cheers,
Shaun

 

[ColinJ]

In ... that ... case ... I'm out!




See ... you ... lot ... tomorrow!

 

[Shaun]

I've stopped fiddling with the import routine now. Back to normal service ...

 

[phil_hg_uk]

Kids eh

 

[Norm]

I've stopped fiddling with the import routine now. Back to normal service ...

Really?

It's still running slowly at times, although it worked fine opening this page - conspiracy theory anyone?

Thanks, Boss, hope the tests went well.

 

[Shaun]

Ah, yes, well ... after I did the first test ... and told everyone I wasn't going to do any more testing ... I sort of did ... but just a bit ...

Cheers,
Shaun

 

[ColinJ]

I've had 30 second delays opening threads on both this and the new test forum this morning.

 

[Shaun]

I've had 30 second delays opening threads on both this and the new test forum this morning.

I notice similar lock-ups and delays myself when using CC, but suspect it is related to the Sphinx search database updater which runs every 15 mins. to index all the new content for 'View New Content'.

[Which is why it takes a little while for new post info to hit the search results page!!]

We won't need the Sphinx updater running once we migrate so hopefully it will eradicate the occasional stalls ...

Cheers,
Shaun

 

[ColinJ]

I notice similar lock-ups and delays myself when using CC, but suspect it is related to the Sphinx search database updater which runs every 15 mins. to index all the new content for 'View New Content'.

[Which is why it takes a little while for new post info to hit the search results page!!]

We won't need the Sphinx updater running once we migrate so hopefully it will eradicate the occasional stalls ...

Cheers,
Shaun

Interesting. I hadn't thought about how the View New Content feature works but I had noticed the delay in reporting, and also the fact that multiple updates to the same thread find their way in.