The test database is exactly the same as the development. I don't know if it matters, but it's a cucumber test, so it's actually the cucumber environment. But that environment is only linking to test, so it should be exactly the same.
$ rake ts:in RAILS_ENV=test (in /home/rejeep/dev/closing) Generating Configuration to /home/rejeep/dev/closing/config/ test.sphinx.conf Sphinx 0.9.9-rc2 (r1785) Copyright (c) 2001-2009, Andrew Aksyonoff using config file '/home/rejeep/dev/closing/config/ test.sphinx.conf'... indexing index 'klass_core'... collected 0 docs, 0.0 MB collected 0 attr values sorted 0.0 Mvalues, nan% done total 0 docs, 0 bytes total 0.005 sec, 0 bytes/sec, 0.00 docs/sec indexing index 'klass_delta'... collected 0 docs, 0.0 MB collected 0 attr values sorted 0.0 Mvalues, nan% done total 0 docs, 0 bytes total 0.001 sec, 0 bytes/sec, 0.00 docs/sec distributed index 'klass' can not be directly indexed; skipping. indexing index 'interface_core'... collected 0 docs, 0.0 MB collected 0 attr values sorted 0.0 Mvalues, nan% done total 0 docs, 0 bytes total 0.002 sec, 0 bytes/sec, 0.00 docs/sec indexing index 'interface_delta'... collected 0 docs, 0.0 MB collected 0 attr values sorted 0.0 Mvalues, nan% done total 0 docs, 0 bytes total 0.001 sec, 0 bytes/sec, 0.00 docs/sec distributed index 'interface' can not be directly indexed; skipping. indexing index 'enum_core'... collected 0 docs, 0.0 MB collected 0 attr values sorted 0.0 Mvalues, nan% done total 0 docs, 0 bytes total 0.001 sec, 0 bytes/sec, 0.00 docs/sec indexing index 'enum_delta'... collected 0 docs, 0.0 MB collected 0 attr values sorted 0.0 Mvalues, nan% done total 0 docs, 0 bytes total 0.001 sec, 0 bytes/sec, 0.00 docs/sec distributed index 'enum' can not be directly indexed; skipping. indexing index 'annotation_core'... collected 0 docs, 0.0 MB collected 0 attr values sorted 0.0 Mvalues, nan% done total 0 docs, 0 bytes total 0.001 sec, 0 bytes/sec, 0.00 docs/sec indexing index 'annotation_delta'... collected 0 docs, 0.0 MB collected 0 attr values sorted 0.0 Mvalues, nan% done total 0 docs, 0 bytes total 0.002 sec, 0 bytes/sec, 0.00 docs/sec distributed index 'annotation' can not be directly indexed; skipping. total 8 reads, 0.000 sec, 32.0 kb/call avg, 0.0 msec/call avg total 32 writes, 0.001 sec, 0.0 kb/call avg, 0.0 msec/call avg Loaded suite /usr/bin/rake Started Finished in 0.000242 seconds. 0 tests, 0 assertions, 0 failures, 0 errors On Oct 10, 10:42 am, Pat Allan <[email protected]> wrote: > If there's only one record, then it shouldn't matter what your range > step is, because Sphinx finds the smallest and largest ids available - > which in this case, are the same number. > > Do you have all the same database indexes on your test db and > development db? What's the output of rake ts:in RAILS_ENV=test? > > -- > Pat > > On 09/10/2009, at 8:00 PM, rejeep wrote: > > > > > I didn't mean that I was trying to index a single record. What I meant > > was that I only had one record in the database for that test. So even > > if there would be some high index, I guess it wouldn't take to long > > anyway. > > > If I try with this conf: > > development: > > sql_range_step: 1000 > > production: > > sql_range_step: 1000 > > test: > > sql_range_step: 1000 > > > It's fast in development, but equally slow in test. > > > It doesn't matter if I use 1000 or 10000000 for sql_range_step. > > > On Oct 9, 5:43 pm, Pat Allan <[email protected]> wrote: > >> Hi Rejeep > > >> Sphinx doesn't allow you to process a single record - only a full > >> index. Also, do you have sql_range_step set for the test environment, > >> as well as the development environment? > > >> -- > >> Pat > > >> On 09/10/2009, at 11:53 AM, rejeep wrote: > > >>> Hi! > > >>> I have a site where I want to test the search. From the test I > >>> create > >>> the records and then create the index. But it's so slow that it > >>> times > >>> out. Yes, I'm using factories and I am aware of the id problem. But > >>> first of all. In the test I only want to index 1 record. And the > >>> id of > >>> that usually is between 1000 - 5000. So that should not be such a > >>> big > >>> problem, right? And even thought I set sql_range_step, it is still > >>> slow. > > >>> Since it is super fast in development the only thing I could think > >>> be > >>> the problem was the id's. But since it's not. Does someone has any > >>> other suggestion? > > >>> If I skip creating any records before the indexing in the test. Then > >>> the indexing is fast. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
