Hi all,

Thanks to Pat, I got the search working properly now. However,
indexing is now giving me a headache...

As explained in my previous threads, I'm trying to index and search
Projects. It worked fine in development, with a very small test
database. However, in production (with tables under 2k records),
indexing seems to take loads of disk space (which is released once
indexing is over). Some examples:

    indexes writeboards.writeboard_comments.body, :as
=> :mr_comment_body (1158 rows, 416kb)
    indexes folders.project_documents.description, :as
=> :file_description (1457 rows, 352kb))

    has memberships.user_id, :as => :member_ids, :type => :multi (652
rows, 56kb)
    has "IF(projects.private = 0, '0',
GROUP_CONCAT( memberships.user_id))", :as => :members_or_public, :type
=> :multi

        requires 1.4GB
        -----------
Now, the same without :members_or_public:
    indexes writeboards.writeboard_comments.body, :as
=> :mr_comment_body
    indexes folders.project_documents.description, :as
=> :file_description

    has memberships.user_id, :as => :member_ids, :type => :multi


        requires 1.1GB
        -----------
Without :member_ids :
        indexes writeboards.writeboard_comments.body, :as => :mr_comment_body
        indexes folders.project_documents.description, :as
=> :file_description

        75MB
        ------------

Obviously, there is an issue with has memberships.user_id, :as
=> :member_ids, :type => :multi




Also, without the :member_ids, adding indexes requires more and more
disk space:
        indexes writeboards.name, :as => :writeboard_name
        indexes writeboards.writeboard_contents.body, :as => :mr_content_body
        indexes writeboards.writeboard_comments.body, :as => :mr_comment_body
        indexes folders.project_documents.description, :as
=> :file_description
        indexes folders.project_documents.filename, :as => :file_name
        indexes folders.description, :as => :folder_description
        indexes folders.name, :as => :folder_name

    requires 1GB of disk space for indexing.

Is that a normal behaviour? If not, has anyone encountered this
problem? Any idea what I should check to fix it?
All my tables are pretty small and  "many indexes" + "member_ids"
always crashes because I do not have enough space on the hard disk.
Will I need 10Gb of disk space for indexing tables with 10k+ rows?
All this is without the use of wildcards, infix or prefix. Enabling
them does not seem to have any effect on the disk space required.

-- 
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.

Reply via email to