postgresql - How much more performant is Postgres than MYSQL on fulltext search? -


I am an MYSQL user, never tried postgres.

But find the bottle neck full text in MYSQL when the data set is very large. I ran a benchmark over a large dataset a few years ago and found that:

MySQL fullvaster

One more drawback is that it inspires Mianjam on you which brings many problems. After the index reaches a certain size, the index update also slows down: When you enter a new line, a significant portion of the index is rebounded, sometimes to include a few hundred megabytes of index for a forum post. Is written. In other words, this is fine for some forums with some small posts, but for one reason Wikipedia does not use it ...

  • PostgreSQL Full Text

MySQL is nearly 10-100x faster than full text, is very powerful, abstract, faster on inserts / updates, there is no problem with locks, in other words it is a completely decent solution.

Although due to the MVCC data set is larger than the RAM slow searches slow down, postgra has to check the visibility of the rows by killing the pile. Note that this may turn into future versions. If your query returns 10 rows, then there is no problem, however, if you want to add SELECT WHERE (integer query) ORDER's date range of 10 and full text to 10.000 lines, then it can be very slow. I'm still faster than SQL, but you do not want to showcase.

  • Zapion: I tested it, Lusen and Sphinx, who have a good reputation.

The Zapion does not have to be compatible with database restrictions, so it can create many opimizations. For example, this single-author is a multi-reader concurrency model, so you will need some sort of update queue to update your index in the background. It has its on-disk format. The result is that it is incredibly fast, even when the dataset is much higher than the RAM, and especially matches many lines on complex queries, and only returns the most relevant ones.

Very large, there are probably several duplicate stuff in it, the result is that there is no need to recover the goods.

Originally once Postgrass started exploring the IO-wall, MySQL was dead for a long time, and the Xapian continued to blaze.

But it is not well integrated into the database, so it has more work to use. If you have a large dataset, then it's worth it only. If this is your case then try it out, it's amazing if your dataset fits into RAM, then postgres will work with very little trouble. In addition, if you want to add full text and database queries, then integration becomes important.


Comments

Popular posts from this blog

c++ - Linux and clipboard -

What is expire header and how to achive them in ASP.NET and PHP? -

sql server - How can I determine which of my SQL 2005 statistics are unused? -