Viewing profile — ruw1090
ruw1090
HN member- Joined
- Wed, Mar 19, 2014, 7:22 PM UTC
- HN karma
- 75
- Public activity
- 27 items
- HN profile
- View on Hacker News ↗
About ruw1090
No profile information was provided.
Recent public activity
-
comment
Comment #44758461
No tax on tips does not apply to payroll taxes (FICA).
-
comment
Comment #42297403
The Xenomorph term wasn't created by the fandom. It was first used in-universe in "Aliens".
-
comment
Comment #42070428
Citation?
-
comment
Comment #32656169
Sure, but given multiple opportunities (every time the clip gets brought up) to condemn it, he hasn’t. This should tell you enough.
-
comment
Comment #32570373
Close, but in database years it was actually already in its mid life crisis.
-
comment
Comment #32089177
The snowflake clusters are several factors bigger (and more expensive) than almost all of the comparison points.
-
comment
Comment #32088605
That makes sense, thanks for clarifying. I got confused by the UI.
-
comment
Comment #32088594
Do you have any benchmark results with Clickhouse in a clustered configuration (and other db's)? Is Clickhouse expected to be run in only single node deployments?
-
comment
Comment #32088361
Yea, Redshift looks like it was run on an ra3.xl (4 cores) and is comparing against clickhouse on a c6a.4xl (16 cores). I suspect if this were normalized Redshift would have an edg…
-
comment
Comment #32088117
There's a lot more involved in an execution engine running complex queries that are not single table group by than just QO (though this is important). It includes things like join …
-
comment
Comment #31898983
The total estimated cost has increased by 44 Billion. Only ~10 billion has been spent on the project so far.
-
comment
Comment #31898959
I stopped reading at "Incredibly, the state has not laid a single mile of track" for California High Speed rail, which is completely false. There are 119 miles under active constru…
-
comment
Comment #19852946
> You are correct however that TimescaleDB requires more storage than some of these other options. If storage is the most important criteria for you (ie more important than usabili…
-
comment
Comment #18394560
To build on the list of features above, here's a blog post from Pandora where they go into the details of what they use MemSQL for and some of the alternatives they looked into for…
-
comment
Comment #18393868
I mean that an operation that needs more memory than is available will fail, but the server itself will remain operational. An simple example would be loading more data into an in-…
-
comment
Comment #18393683
If you have an example of the query you thought was returning inconsistent results, feel free to make a post over at https://www.memsql.com/forum/ with a repro.
-
comment
Comment #18392898
The best thing to do in this situation would be to set the maximum memory on the MemSQL server via the `maximum_memory` system variable. The server will then internally manage it's…
-
comment
Comment #16747713
> data allowance of 10 million rows, and range up to a 100 million row allowance. Only supporting up to 100 million rows seems extremely limiting for a lot of analytics use cases. …
-
comment
Comment #15914950
The other thing that is misleading about this benchmark is that the comparison page shows results for many different DBs on vastly different hardware without any mention of price. …
-
comment
Comment #15822187
What is the benefit of shipping data to the GPU for execution if the data is on S3 or HDFS? Won't most of the cost of the query be I/O?
-
comment
Comment #15435717
It looks like you had to rewrite the queries pretty significantly to get them to run on all three. Redshit/Bigquery don't support rollup/grouping sets/intersect/except etc. which t…
-
comment
Comment #13992244
So blazing db mainly uses gpus to speed up compression/decompression? How do gpus help with partitioning and data skipping?
-
comment
Comment #13864084
citation?
-
comment
Comment #12716362
very interesting. Do you have a link to documentation? I'd like to take a look before I try it out.
-
comment
Comment #11910011
It looks like they benchmarked against MemSQL 3.2, which is nearly 2 years old and Hive .11, which is close to 3 years. Not sure how out of date the other comparisons are.