Hi,
We're seeing a situation on our servers, wherein under high
concurrency, multiple
instances of searchd are spawned and immediately killed, almost like
an instance per
query. Due to this process, we're observing a high load on the server
4.something and
delays in our reply times of over 1/2 seconds. Even though sphinx
takes only 0.something
seconds to reply and rails takes 0.0something to process the request.
Here's the generated config file we're using.
indexer
{
}
searchd
{
address = 127.0.0.1
port = 3312
log = /path/to/log/searchd.log
query_log = /path/to/log/searchd.query.log
pid_file = /path/to/log/sphinx.pid
max_matches = 500
}
source deal_core_0
{
...
}
index deal_core
{
source = deal_core_0
path = /path/to/db/sphinx/production/deal_core
morphology = stem_en
charset_type = utf-8
}
index deal
{
type = distributed
local = deal_core
}
Any help would be appreciated.
Thanks,
Sid.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Thinking Sphinx" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/thinking-sphinx?hl=en
-~----------~----~----~----~------~----~------~--~---
