Thunderstone Support Forums

Hi

We have a timeout problem related to categories which seems to have appeared recently (i'm not sure about the recently though).

We have a profile which indexes about 185 000 pages and has 10 categories (nothing fancy, just 1 or 2 url roots each.

When i do a search on a single word letting "everything" selected, i get a result (about 2000 hits for one example) in 1 or 2 seconds. If i choose a category i get nearly all the time a timeout.

I had noticed before occasional timeouts for complicated queries, but the index was still building, but now it is complete, there are no walks and replications running.

Whats going on?

Do you have any idea roughly how many pages per category (in particular the category you're searching)?

Are your appliance scripts up to date?

Try turning on "Fast Result Counts" to see if that makes a difference.

Hi

Size of the category does not seem to matter.

The range from about 1000 pages to 95000 pages, and the result is the same for all of them.

Scripts are the very latest...

Switching 'fast result counts' on gives strange results

For the 2 big categories (95000 and 60000) i get results, but for the small ones i still get mostly tmeouts.

Hi

Any news?

Trying to replicate it...

Did you have chance to replicate the issue ?

It has been one week we are waiting for your help in resolving this issue...

Could you please give us some news on this issue ?

No luck replicating it so far. Even using a 3 million page profile.
What's your system load average (Maintenance->System Information->Load)?
What non-default search settings are you using?

The system load average is the following :
9:23am up 33 days, 15:13, 0 users, load average: 1.00, 1.02, 1.00

The search settings we have changed are the following :
(default -> Changes)
Enable Sherlock: N -> Y
Max Docs to Auth-Check: -1 -> Not used
Total Auth Timeout: -5 -> Not used
Debug Results Authorization: N -> Not Used
Number of Suggestions: 3 -> 2
Synonyms: Phrase Recognition only -> Phrases & use synonyms by default
Allow the @ Operator: N -> Y
Allow Linear : N -> Y
Allow Post-Processing: N -> Y
Allow "WITHIN" Operators: N -> Y
Word Forms: Exact match -> Plural & progressives
Word Proximity: medium -> high
Visible: N -> Y

I hope you will be able to give us a solution soon.
Thanks

Looks like your system is consistently busy. Please open a tech support ticket and attach your tech support info page.

Hi !

I'm facing the same issue again.
Last time you created a new index by using a webex connexion.

Could you please do this again ?
May be we can schedule an intervention on monday.
Let me know

I expect to have a patch to fix this issue but it seam this patch is still not available...

Thansks for your help.