We have about 60,000 URLs in total... and only about 2,300 are indexed... I
think that the problem is not really in the DB, i think that it is more of
an indexer problem, stalling at URLs that to not answer, and maybe stopping
in the middle of indexing...
I have let 3 indexers run for about 1
What front-end and storage mode do you use?
Roy Nasser wrote:
We have about 60,000 URLs in total... and only about 2,300 are indexed... I
think that the problem is not really in the DB, i think that it is more of
an indexer problem, stalling at URLs that to not answer, and maybe stopping
Hi Alex,
I am using multi-crc, and I tried accessing with the PHP frontend, and with
the CGI frontend... (I believe it is a C script... the one that goes in the
bin/ directory of the compiled source)
-Original Message-
From: Alexander Barkov
To: Roy Nasser
Cc: 'Shane Wegner '; ''[EMAIL
1) Check that you have configured search template to use crc-multi
with DBMode command. Note that it is "crc-multi", not "multi-crc".
2) Check queries being sent to backed using MySQL queries log.
3) You may compile search.cgi with SQL debug:
export CFLAGS=-DDEBUG_SQL
./configure
Hello, Craig.
Thank you very much for this technology description.
I think we should put it into documentation supplied with
UdmSearch. What do you think?
P.S. I'll try to test this as well with search.cgi to find
and fix possible problems.
Craig Small wrote:
G'day,
A requirement for
I took a look into search.cgi sources and made some fixes
which makes CGI ÅÝ be able to process negotiation too. Installation,
making symlinks and apache configuration scheme is exaxtly the same
with PHP front-end.
Craig, Thanks again for nice idea.
P.S.
It will be include in 3.1.6
UdmSearch version: 3.1.1.2
Platform: Double Pentium III
OS:Linux
Database:
Statistics:MySQL
Apache 1.3.12 - PHP 3.0.16
Warning: Variable used in global statement already exists in the function in
common.inc on line 174
Query error: SELECT
This discussion has been quite valuable - as more people really push
udmsearch, these performance issues will become more important. What is
the "best" option for performance, given the database engine being used?
Or should one just use the crc-multi mode with flat files? I'm sure the
answer for
Hi!
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
From:Maciek Uhlig [EMAIL PROTECTED]
To: Udmsearch@Search. Udm. Net [EMAIL PROTECTED]
Date:Tuesday, October 03, 2000, 12:35:15 PM
Subject: UdmSearch: PHP frontend: unknown option in parse.inc
