is possible to cut the profil table for optimise search

Hi all

is possible to cut the profil table for a male table and a separate female table for optimise search sql,

it seems realy apropriate no?! How to do that please 

thanks for help

Jessica

 RE:

Easy.... simply rewrite the entire Dolphin code base.

Considering dolphin is not written for separate male and female tables the answer would be no. Not with out a lot of rewrites.

And you would have to explain to me why you feel that would improve sql performance. If fact, a lot of areas such as pulling a list of members that fall within parameters other than gender it would make matters worse as two tables would have to be queried instead of one. So i really do not see a performance improvement at all.

But when you havé 50 000 membres ,y for a datting site for exemple, you search only Man. Or only woman, ils it ont more speEddy to search on 25000 lines ?! Why dont duplicate thé profile table for table Man. And table woman ?!

That will only improve performance for searches that are specifically for male or female. The moment you try to search for something else such as last reg date or date of birth or any of the other profile fields the two tables would have to be searched instead of one.

And besides, we already told you it could not be done anyway. Dolphin was not written that way.

If you want to improve performance on male/female searches then add a sex index to the table. Thats what indexes are for. There is no need to split the tables.

http://dev.mysql.com/doc/refman/5.0/en/mysql-indexes.html

That will only improve performance for searches that are specifically for male or female. The moment you try to search for something else such as last reg date or date of birth or any of the other profile fields the two tables would have to be searched instead of one.

In the case With a dating concept, who man table have only access to woman table , you wrong ;

It provide a big improving performance , you can test it with a workbench..

Secondly, putt indexes for male and female will decrease performance, not improove..

SO my question was, IS the dolphin team plan to do that in the roadmap, who seems very apropriate

in all cases ; 

In the context of a social website, there are no pb to have 2 table, if the base structure is correct it will

no decrease perf, and in the majority cases (dating) , it will improve so much !

HAve a nice day ;)

jessica

IANAL

BoonEx has no plans to split the profile tables like that.  You can spend the thousands of dollars needed for a developer to hack-away at the script and make that kind of database structure work, but as Deano pointed out, it's not worth it.

This is one of the most misguided and uninformed requests I have seen and I'm surprised it has gone past more then one reply.

A number of people have given very valid reasons on why this is a bad idea. And Boonex did this the right way from the start. They took many short cuts, but this was not one of them.

MySQL is very fast for this kind of thing and can handle millions of records with the proper queries, indexes, RAM and fast 'disk' access.

If you want to speed up your site start with your MySQL config and server setup. Using Nginx and xCache will free up more CPU and RAM for MySQL.

If you want to speed up everyone's sites the hire someone to analyze and optimize the SQL quires coded into Dolphin and add/change indexes where appropriate.  Then move on to improving the dolphin caching system so those improved quires have to be run less often.

Or... Do what most people do and get a faster server.