neildahlke

The problem has a name, and its name is Dean Preston.

I wonder when HN gets to the stage that all the negativity is directed towards Austin instead of San Francisco, and when we see all the posts about how tech is ruining Austin.

This is an absolutely horrible response by someone who clearly doesn’t live in the area.

PG&E has constantly prioritized shareholder profits over renovating their aging infrastructure. They caused the biggest wildfire in the history of California and are now _finally_ facing a reckoning for their reckless and destructive behavior.

Fix your goddamned infrastructure and get a smaller bonus. That’s what we want.

I've seen you mention these inconsistent results twice here in this this thread, but have worked at MemSQL for 5 years and never heard of such an issue. Have you reached out to see if maybe your query / data is not what you expect? I've seen inconsistent results only once, and it was because the default date formats across RDMBSs were different (and was not anticipated).

I believe you're conflating the name with the actual contents of the post. The demo uses the MemSQL columnstore, which is disk-based and leverages memory only for indexes, metadata, query processing etc.

Point of clarification - MemSQL does not need to be all in-memory, there is also a columnstore that is on-disk and only leverages memory for indexes / column segment information.

Would something like this help you?

https://www.youtube.com/watch?v=8XSf6XfYl64

Developed by a former colleague at http://near.ai/.

Feel free to reach out to me on our public Slack channel to clear up anything that is fuzzy! I'm an engineer at MemSQL and want to know (1) how I can help and (2) how we can provide non-fuzzy information to the rest of the community.

Channel: chat.memsql.com My UN: eklhad

MemSQL engineer here.

No, we do not offer appliances. We are a software only solution. I do not know of any deployments where RDMA is being utilized today. I'm interested in your use case. If you're so inclined, join chat.memsql.com (my UN is eklhad) and we can converse a bit more rapidly.

Hopefully it isn't. In the event that something goes wrong, we need him here.

This seems like very poor timing given the most recent gorilla entering their room.

Essentially, we fed audio out from an Android phone through a mini audio amplifier, then soldered from the amplifier directly in the Furby's speaker.

I was one of the hackers on the project, if anyone has any questions, shout out!