Konstantin Osipov ([info]kostja_osipov) wrote,
@ 2007-03-10 00:51:00
Previous Entry  Add to memories!  Tell a Friend  Next Entry
Features added in 4.1, 5.0, 5.1
While reading "Crossing the Chasm" by Jeffrey Moore, I discovered that I never actually questioned the features we added in the recent releases.
I came to MySQL with a background similar to Peter Zaitsev's, we worked together in Spylog. MySQL was used there as storage for an in-house scale-out application that served TBytes of data per month and hundreds of thousands of requests per day.
The thing is, almost none of the features implemented in the recent years I would use for that sort of appliance.
Top things on my list would be:
- integrated inverse indexes/full-text search, both InnoDB and MyISAM. And these indexes would need to scale well to give low response times for at least 500 MB tables.
- scaling to multi-core CPUs and high amount of memory (64GB and more)
- better and faster networking that would not spawn off a thread for every connection, so that the server can actually handle a connection per user.

So what would I use? Prepared statements, maybe, only if they were noticeably faster. Mixed mode replication, that's for sure. Extended character set support? Hardly, I'd probably run the system in pure Unicode.

It seems we were trying to add all these stored procedures and triggers to appeal to some ERP systems and to become a viable replacement for some extinguishing behemoths like Sybase/whatever.
The thing is, we're not there yet, and I don't know when we will be.
I wonder if any of the modern Web 2.0 system is using this stuff.

Huh.



(8 comments) - (Post a new comment)


[info]dkfl
2007-03-09 10:02 pm UTC (link)
Sad to hear this.

(Reply to this) (Thread)


[info]kostja_osipov
2007-03-09 10:23 pm UTC (link)
Well, they are not totally useless after all, and at sometime we'll get there :)
Just doesn't seem to be the wisest use of our time. The thing is, perhaps, that when we set off we didn't know how difficult the road is going to be.

(Reply to this) (Parent)

Other features to consider
(Anonymous)
2007-03-09 11:05 pm UTC (link)
Kostja,

what about VIEWs? I heard from some friends that they absolutely love having VIEWs in MySQL. They are not highly optimized yet, but very helpful in mid size projects. They reduce the programming effort a lot.

(Reply to this) (Thread)

Re: Other features to consider
[info]kostja_osipov
2007-03-09 11:36 pm UTC (link)
Yes, why not... Beware of some gotchas when using views and replication (I have in mind Bug#25144). But we will fix it too one day!

(Reply to this) (Parent)


[info]vmgor
2007-03-11 05:38 pm UTC (link)
А зачем вообще нужен MySQL? Вроде бы, за последние несколько лет Postgres стал работать побыстрее, для простых задач есть всякие SQLite и Derby. Это из раздела "забесплатно". В разделе "за деньги" тоже, в общем-то далеко не пусто...

(Вопрос именно про субд. MySQL ABI я знаю зачем нужен :)

(Reply to this) (Thread)

Это провокация :)
[info]kostja_osipov
2007-03-12 10:05 pm UTC (link)
Если серьёзно, есть вполне конкретные причины зачем он нужен.
К примеру то, как у нас работает репликация.
А вообще, не знаю. Правильнее наверное пытаться понять не зачем, а почему.

(Reply to this) (Parent)(Thread)

Re: Это провокация :)
[info]vmgor
2007-03-13 04:53 am UTC (link)
А в Постгресе не работает?
Это не провокация, мне действительно интересно.

(Reply to this) (Parent)


[info]jabrusli
2007-04-21 08:10 am UTC (link)
Слежу за раработкой и вижу что реализуются какие-то псевдо-фичи. Они вроде бы всем нужны, а реально их никто не использует.

Лучше бы сделали Storage Engine как MyISAM, только допускающую грязное чтение. Т.е. чтобы SELECT-ы не лочились при делитах и апдейтах, и читали хоть что-то (старые или новые данные, не важно). В 99% веб-приложений это приемлемо. Нагрузку, вызванную локами, ожиданиями и простоями, снимет значительно.

(Reply to this)


(8 comments) - (Post a new comment)

Create an Account
Forgot your login or password?
Login w/ OpenID
English • Español • Deutsch • Русский…