| Time |
Nick |
Message |
| 07:26 |
|
BDorsey joined #evergreen |
| 07:28 |
|
collum joined #evergreen |
| 08:00 |
|
redavis joined #evergreen |
| 08:30 |
|
mmorgan joined #evergreen |
| 09:13 |
|
collum joined #evergreen |
| 09:40 |
|
Dyrcona joined #evergreen |
| 09:42 |
|
tlittle joined #evergreen |
| 10:01 |
|
sleary joined #evergreen |
| 10:16 |
|
stompro_home joined #evergreen |
| 10:52 |
|
briank joined #evergreen |
| 12:17 |
|
jihpringle joined #evergreen |
| 13:47 |
|
jblyberg joined #evergreen |
| 13:53 |
|
sleary joined #evergreen |
| 14:31 |
jeffdavis |
I'm finding the search.symspell_suggest function is incredibly slow on real-world data. In my test environment, this query adds ~23 seconds to a keyword search: SELECT * FROM search.symspell_suggest( 'rainbew', 'keyword', '{}', NULL, '2' ) |
| 15:21 |
|
jihpringle joined #evergreen |
| 16:18 |
|
jihpringle joined #evergreen |
| 17:05 |
|
mmorgan left #evergreen |
| 17:05 |
|
stompro_home joined #evergreen |
| 17:17 |
|
stompro_home joined #evergreen |
| 17:41 |
|
jihpringle joined #evergreen |
| 17:58 |
jeffdavis |
hmm, waaaay too many suggestions being processed by search.symspell_lookup, wonder if some settings are askey |
| 17:58 |
jeffdavis |
*askew |
| 18:51 |
jeffdavis |
not obviously a setting thing - even with the default values everywhere I can think of, this query processes over 62,000 potential suggestions (which takes 23s): SELECT * FROM search.symspell_lookup('rainbew','keyword'); |
| 18:52 |
jeffdavis |
this is in an environment with 4M non-deleted bibs and 7.2M entries in search.symspell_dictionary |
| 19:47 |
|
jihpringle joined #evergreen |
| 20:01 |
|
eglogbot joined #evergreen |
| 20:01 |
|
Topic for #evergreen is now Welcome to #evergreen (https://evergreen-ils.org). This channel is publicly logged. Logs for today: http://irc.evergreen-ils.org/evergreen/today |
| 20:05 |
|
jweston joined #evergreen |
| 20:05 |
|
pinesol joined #evergreen |
| 20:08 |
|
stompro_home joined #evergreen |
