[HN Gopher] MySQL Raytracer
___________________________________________________________________
MySQL Raytracer
Author : bane
Score : 116 points
Date : 2022-08-11 00:06 UTC (1 days ago)
(HTM) web link (www.pouet.net)
(TXT) w3m dump (www.pouet.net)
| bratao wrote:
| That is just incredible. Just a rant, I test multiple databases
| every 6 months and I think that MySQL is unfairly treated because
| of Oracle acquisition. For my use-case (store TBs of structured
| text data, single writer) there is no better (considering
| performance, replication and compression) than MySQL 8 with
| MyRocks engine (https://docs.percona.com/percona-
| server/8.0/myrocks/index.ht...)
| [deleted]
| Alupis wrote:
| Unless you need commercial support from Oracle, I just don't
| see a reason to run MySQL over MariaDB these days.
|
| MariaDB has been a drop-in turn-key replacement for us in every
| case... the MySQL drivers even work with MariaDB as the
| backend.
|
| Nearly everything (perhaps everything) MySQL does, MariaDB has
| or has had long before MySQL got around to it. Nearly all
| (perhaps all) commands work exactly the same, which means any
| support doc or query you might want to run can operate on both
| without issue. You can even get commercial support for MariaDB
| from several companies including the very organization that
| makes it.
|
| Not to mention, most of the original MySQL team works on
| MariaDB.
|
| So, other than the folks that don't know or don't care about
| the history... why would someone go out of their way to choose
| MySQL these days? Is this the "OpenOffice" effect perhaps?
| dspillett wrote:
| _> MySQL is unfairly treated because of Oracle acquisition_
|
| That, and the history of doing things "wrong" for the sake of
| performance, and the community banging on about how those of us
| caring about the _data_ were just being picky123, from long
| before Oracle came along. myISAM was the default for far too
| long.
|
| _> MySQL 8 with MyRocks engine_
|
| For those concerned about Oracle, there is of course MariaDB
| which also supports MyRocks.
|
| I'm not sure what the current state of play is, but for a while
| at least MySQL was slower moving than MariaDB, getting CTE
| support (in production ready releases) a couple of years later
| for example.
|
| ---
|
| [1] just implement FKs in your own code!
|
| [2] why is 2005-02-31 being sent to the database anyway, why
| should it check for valid dates?!
|
| [3] ... you postgres/sql-server/other people are just expecting
| things the application should deal with, look how fast this is
| at bulk inserts compared to your "properly"!
| dbt00 wrote:
| http://sqlanywhere.blogspot.com/2008/03/unpublished-mysql-
| fa...
|
| for those of us who are old enough to remember actual
| internet flame culture, this is an amazing late example.
| icedchai wrote:
| To be fair, MyISAM hasn't been the default since MySQL 5.5...
| which was released over 10 years ago. I stopped using MySQL
| in favor of Postgres quite some time ago, so not sure about
| the current data validation / integrity story, however.
| sroussey wrote:
| Admittedly, those items could be dealt with at the
| application later, and for that price you got something very
| fast.
|
| And fast back then meant cheap. Hardware was more expensive
| than people. It's reversed now, of course, and we want extra
| layers and thing to make developers more productive. But back
| in the MySQL heyday, that was not the case, and I for one am
| glad something like it was around.
| radicality wrote:
| The Facebook way! Almost all DBs at FB are MySQL (slightly
| custom) with MyRocks.
| WesleyJohnson wrote:
| I've never heard of MyRocks. I'm going to look into it some
| more, but if we're using MySQL as a regular ol' relational
| database, backing Django, is there anything to be gained from
| looking at MyRocks? We don't really do document stores, and
| only have a handful of JSON fields.
| tehalex wrote:
| Probably not - unless you are very write heavy and having
| problems scaling MySQL as-is.
| kirisakow wrote:
| This thread is a duplicate of the 2019 thread
| https://news.ycombinator.com/item?id=21218144
| dang wrote:
| Reposts are ok after a year or so!
| https://news.ycombinator.com/newsfaq.html
|
| (It was reposted in April 2022 too -
| https://news.ycombinator.com/item?id=31167205 - but didn't get
| significant attention. That's the other variable.)
| remram wrote:
| The source seems to be rather imperative:
| https://gist.github.com/remram44/755302174c912a004f8c839f3c8...
| chuckledog wrote:
| Imperative and eschewing of newlines... maybe change the
| subject line here to "25-line MySQL Raytracer" ;D
| 10us wrote:
| Here's a direct link to the youtube video showing the result:
| https://youtu.be/U5Tk1H5C4xI?t=75
| dang wrote:
| Related:
|
| _The most advanced MySQL raytracer on the market_ -
| https://news.ycombinator.com/item?id=21218144 - Oct 2019 (47
| comments)
|
| _MySQL Raytracer_ -
| https://news.ycombinator.com/item?id=21199895 - Oct 2019 (2
| comments)
| programmarchy wrote:
| Okay not bad, but can you implement Doom in MySQL? ;-)
___________________________________________________________________
(page generated 2022-08-12 23:00 UTC)