Hacker Newsnew | past | comments | ask | show | jobs | submit | shub's commentslogin

Sounds like they can do predicate pushdown to the storage nodes now. And...mainly beneficial for medium-to-highly selective scans of mostly uncached tables?


I am a dataologist, even if my title says software something something. Commercial software development is about getting data from point A to point B more than anything else. There's a little bit of logic, a little bit of munging, but almost all of what could be called an algorithm is done by a library or some other system--probably a database. It's maybe once a year that doing something algorithmic, e.g. reduce a regex to a hand-coded FSM, or write an exponentially decaying counter, is actually the best thing I can do to solve the problem at hand.


IOCP doesn't do it[1]. Well, if it does then it's not documented. You can post custom completion packets so at first glance it looks easy to make open/close be async...I think there is probably a good reason why NT won't do that for you.

That's pretty awesome though, that you have to worry about latency of open().

[1] https://docs.microsoft.com/en-us/windows/desktop/fileio/i-o-...


Reminds me of an IBM technical bulletin I found, somehow, about 10 years ago. It advised that if you were moving from this z9 hardware configuration to that one, you would have 30 minutes of downtime. Implying that other changes required no downtime, which I inferred wasn't stated because it wasn't insanely awesome to mainframe guys, adding CPUs and RAM to a running system was just how things worked.

I was in college at the time and looked at job postings for mainframe programmers because I wanted to work on that. Never found one that required less than 5-10 years experience, not then and not when I've checked every couple years after that. Too bad; I quite liked the idea of working in an ecosystem that starts from "let's make this work every single time" instead of "let's make this work well enough to keep customer complaints to a dull roar".


If you're using Spark's built-in scheduler then the cluster manager is a SPOF. Hadoop docs say you can get active/standy ResourceManager, not that I've tried it. Spark can also use k8s and nomad to schedule executors, and those have HA modes as well. I assume Mesos does HA.

You're still boned if the driver dies. I am pretty sure that the driver keeps some important state in RAM so if the node hosting it goes down you have to restart from the beginning, even if the cluster manager restarts the driver.


In addition, a lot of the techniques used to write high-performance Java boil down to "write it like C". Avoid interfaces, avoid polymorphic virtual calls (as you can't avoid virtuals entirely), avoid complex object graphs, avoid allocating as much as possible...it's not nearly as nice as naive Java. Still nicer than C IMO. If your process segfaults you can know for certain that it's a platform bug.


The other thing that makes Java nicer than C is the ease and depth with which you can profile it to discover where the bottlenecks actually are. While it's certainly possible to profile in both cases, the runtime reflective and instrumentation capabilities of the JVM really add a lot of power to it.


The short excerpt you can read for free says this is more about stuff like the two minutes between clocking out at closing time and locking the door on your way out. It might be wage theft in some sense but isn’t the same thing as requiring hours of unpaid overtime. On the other hand, I suspect the part of the article you can’t read for free is about an employer who tried to cover a substantial amount of work under this exemption and now the court has to ruin things for everybody to prevent abuses.


It might be OK if everything goes well.

My own experience closing down stores of different types, though, is that that time varies. Most of these places won't let you clock in just a tad early: One place required you be perfectly on time, many others had a 3-minute window before your scheduled time.

Now, if locking the door and leaving took a minute each time (much like employees leaving without locking up), it might not be an issue. But lots of things happen. Sometimes you have to wait for folks to use the toilet: Other times, there are issues with the alarm and you wind up having to call the alarm folks. Sometimes it just takes longer to leave: One fast food place I worked at required folks gather in one vestibule. 2 workers went to their cars, one stopping outside the door and the other stopping at the exit.

This was a security measure in case of a robbery. You were encouraged to clock out once your work was done, though, and wait around for the others and management to get finished as well. You were violating safety standards if you just left.

This was all unpaid time. Even at 5 minutes each day, it adds up. Sure, it ism't the same as requiring hours of unpaid overtime, but that's only due to severity of wage theft. It is like having a lesser punishment for stealing $5 compared to $100.


It's "4-10 minutes" per day over 17 months.


Why, on the off chance one flies into someone’s open mouth and the surprise triggers a swallowing reflex? I wouldn’t have a lot of sympathy for an adult who ate the homemade pills a guy threw at him and then suffered serious side effects.


I'm surprised I have to argue about whether it's irresponsible to throw dangerous things into a crowd. It's irresponsible because they're dangerous.

He can't be sure what will happen with pills that people accidentally carry out on their shoes or clothing. Any pills that don't get cleaned up from the venue could be eaten by children or animals at a later date.

We're talking about a drug that we don't even let sick people buy until they've talked to a doctor and a pharmacist. Maybe someone in the crowd wrongly believes that they need it or rightly believes that they need it but doesn't know how to take it properly.

Also, if you don't have sympathy for an adult who eats homemade pills and suffers from it, then you're pretty much arguing that this whole plan is irresponsible from the start.


> if you don't have sympathy for an adult who eats homemade pills and suffers from it, then you're pretty much arguing that this whole plan is irresponsible from the start.

I have plenty of sympathy for an adult who is forced to take homemade pills to save their life. An adult who swallows random pills a stranger threw at them, not so much.


Maybe that commenter is using the same logic that distributing guns to anybody is fine, misusing guns is a personal failing.


You're really stretching to find negative consequences there.


What easy-to-reckon category do you assign the vast swathes of youths who might occasionally be easily convinced to take or buy drugs from strangers in the street?


Hanlon's razor?


Can you maybe explain to me how that could be applicable here?

I’d like to know of a vaguely plausible thought process that would result in this implementation.


That's why I took 102. They give you the straight dope there.


Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: