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

> He is limited by not having an "expensive macbook with 4 real cores" ?? He gave up on a test because it "paged out the 15GB of data".

Note that he already demonstrated that for many of the tests, his older MacBook was faster than these 160 core clusters. There were a couple where the older MacBook was not faster than a 160 core cluster, but he suspects that a newer one might be.

The one that paged out happened to be one where he artificially broke it up into 160 pieces to simulate what it would be like if he had 160 similar cores, but that caused enough issues with memory locality that swapping dominated the results. This artificial partitioning was to give a sense for what results on a 160 core cluster "should" be, but the swapping distorts the results enough that for that problem it wouldn't even be a very good rough estimate.

> Is this guy for real?

This isn't supposed to be a publication-quality paper. This is a blog post, using the resources he has immediately at hand, to show why if you follow cutting edge distributed database research you might be led down a wrong, and very costly, path, which you could avoid with a much simpler implementation on much cheaper hardware.

Note that he references an earlier paper that he did publish on this topic; this blog post is mostly just doing a similar check on some more recent published work, to see if much has improved in the field:

https://www.usenix.org/system/files/conference/hotos15/hotos...


The problem being written about is that the city itself has so little income and revenue that it can't provide certain basic services, and even can't necessarily partner with non-profits which are trying to address problems in different ways.

With a different government, tax base, and so on, Detroit as a whole may have similar problems, but the scale is different, and the larger scale likely means that there are some things Detroit can do that Highland Park cannot.

I'm not sure why you think that an article about one city, Highland Park, should have been about a different city, Detroit, that while it is close by, operates at a very different scale?


> I'm not sure why you think that an article about one city, Highland Park, should have been about a different city, Detroit, that while it is close by, operates at a very different scale?

Well, I did ask the question and not state it as my opinion, didn't I? And I read the article, and already explained my take on the arguments you're making. Are you asking why, or just making a point?

The Detroit native in this thread agreed that Detroit natives think of Highland Park as part of Detroit.

Highland Park is entirely contained inside the Metro Detroit boundary. Use of the word "city" here is overloaded. To an outsider, Detroit is a city and Highland Park is a neighborhood within Detroit. To the Highland Park government, "city" has a technical boundary meaning that is not necessarily relevant to people outside Highland Park, and especially to people outside Michigan.

I'd speculate that most people who don't live in Michigan reading an article about a city in Michigan would assume or imagine something geographically distinct from other cities, with fields in between them, as opposed to a continuous metropolitan area.

My question is whether there might be some political context to the way this article is written. Do you know of any?


Enclaves and exclaves aren't totally unheard of:

https://en.wikipedia.org/wiki/Enclave_and_exclave

They are sort of a topic of interest/amusement, because they aren't the usual thing.

Hamtramck is another city surrounded by Detroit, except for the portion that borders Highland Park.


But it is a distinct city. With a separate mayor, a separate budget, and so separate issues that it has to deal with due to its budget shortfalls. Including issues with the City of Detroit being one of its creditors, due to unpaid water bills.

It is not uncommon for there to be cities or towns in the metro area of other cities that are independent. For instance, Cambridge is different than Boston; or for an even closer example, Brookline which is surrounded on three sides by Boston is independent from Boston. Or Oakland is not San Francisco, nor is Almeda Oakland.

Or for other examples of being completely surrounded, the Vatican is not Rome. Monaco is not France.

The "technical boundary" is not irrelevant here. We're talking about different jurisdictions, with different governments, and an article about how one government is failing to provide some basic services is distinct from another government that is close by but has very different issues due to the differences of scale and available tax base.

> with fields in between them, as opposed to a continuous metropolitan area.

But that's not how cities work. It is very common for two cities to be part of one continuous metropolitan area, and the only way you notice the boundary is by paying very close attention to signs as you pass them.

> My question is whether there might be some political context to the way this article is written. Do you know of any?

I think that the context for this article is just that it's an interesting phenomenon; this small city, which grew very fast during the auto boom and has been fading slowly ever since, and now the government is so cash-strapped that it doesn't even have the personnel to work with independent non-profits to do things as basic as keeping the streetlights on, but also due to the small scale it's possible for individuals and neighborhood organizations to provide some of their own services that the city can't.

The issue of "the government barely exists", as expressed in the title, is not true of Detroit as a whole. While the Detroit government does have issues of being short on funds, it is large enough that there is a recognizable government that is able to do things. But for this small city, which grew very quickly and then has slowly been fading away, the size and scale make it very hard to have a functioning government that can reasonably govern.

And while the state and the federal government obviously do exist, for many of the things that ail Highland Park, the state and federal government generally work by providing grants to cities and towns, but being as cash strapped and small as this city is, it's hard for it to take advantage of programs that could bring in more revenue.


It is a separate city, that is surrounded by Detroit except for one small portion touching Hamtramck which is also surrounded by Detroit: https://en.wikipedia.org/wiki/Highland_Park,_Michigan

It's not terribly uncommon for a city like Detroit to annex surrounding towns and cities, but some of them hold out, which looks like is what happened here.


Those aren't all of the instructions for apt-get. The full instructions are on https://docs.microsoft.com/en-us/sql/linux/quickstart-instal... and appear to consist of:

  curl https://packages.microsoft.com/keys/microsoft.asc | sudo apt-key add -
  sudo add-apt-repository "$(curl https://packages.microsoft.com/config/ubuntu/16.04/prod.list)"
  sudo apt-get update
  sudo apt-get install -y mssql-server
  sudo /opt/mssql/bin/mssql-conf setup
  sudo apt-get install -y mssql-tools unixodbc-dev
  echo 'export PATH="$PATH:/opt/mssql-tools/bin"' >> ~/.bash_profile
  echo 'export PATH="$PATH:/opt/mssql-tools/bin"' >> ~/.bashrc
  source ~/.bashrc
And at that point, you have a limited period trial license of a release candidate version installed, and so once you want to use it for production, you have to start dealing with license management issues, which could limit your ability to easily set up dev envs, test envs, hot spares, etc.

All of that is on top of the issues of how heavyweight it is due to containing a platform abstraction layer that consists of a very large amount of Windows running in user mode, as discussed by others in this thread.


Yes, you have to add the repo, the same as if you wanted the latest postgres bits on any distro. You also have to edit configs for both and you can also choose to install extra tools for both.

I'm surprised at how many people seem to have taken issue with a simple comment. Postgres is easy to install... and now so is MSSQL compared to the complex slow GUI installer they had before. Maybe it'll help the original commenter, maybe not. Let's just leave it at that.


Debian and derivatives have it in repos by default. Please don't make claims like those.


That's more to do with the OS than the DB, and many repo entries are outdated. MSSQL hasnt existed on Linux before, but either way:

> I'm surprised at how many people seem to have taken issue with a simple comment.


Due to Microsoft SQL Server licensing, I would be highly surprised if any Linux distribution were to make it available by default in their repositories.


It's not that the OS supplied versions are outdated. They are updated whenever a minor release comes out.

The thing is, that you must migrate your database between major pgsql releases and you don't want your distro to force it on you. The community pgsql repo has the same rules - you have separate repo for each major release, so no surprises either.


I have an SSD (along with a USB SATA enclosure to connect it), a spinning disk, and at least one USB thumb drive in my bag that I bring to work every day (along with my laptop).

This is in part because I switch between working from home and working at the office fairly often, have travel time in between, and need to have access to more VMs than I can fit on my laptop's internal SSD comfortably.

I also may have SIM cards rattling around somewhere; when I travel internationally, I buy a local prepaid SIM, and I may have older SIM cards left over from the last time I replaced one.


It's valid for your usecase, but I still agree with your parent comment that your bag's contents are unusual.


> and need to have access to more VMs than I can fit on my laptop's internal SSD comfortably.

Exactly the same with me, I regret only getting the 256GB internal drive with my Thinkpad but I wanted the 2560x1440 so I had to trade something off (since it's a personal machine not a work machine), I suspect I'll be upgrading it before long.


No, he said:

> I ran a simple HTTPS web server with net/http, loaded a page on Chrome, and instead of causing a kernel panic...

Followed by demonstrating it working.

However, the point remains that he only got it working up to doing a toy hello world. The part that would be important for performance would be what he mentioned isn't finished, which is allowing it to be used with sendfile so that web servers can just sendfile over a TLS connection and let the kernel handle all of the IO.


What does WeChat do that isn't handled by other, separate apps?

For instance, I don't really see a need to have the same app do chat and payment (in fact, I'd prefer if they didn't).

What about WeChat is particularly innovative, other than just bundling a lot of different functionality into one big app?


> For instance, I don't really see a need to have the same app do chat and payment (in fact, I'd prefer if they didn't).

You not seeing a need and them meeting one that clearly exists have nothing to do with each other.

> What about WeChat is particularly innovative, other than just bundling a lot of different functionality into one big app?

Making it actually work well enough for millions of people to use it. I can't think of anyone else who's succeeded at that and there are plenty that failed miserably to build that type of "kitchen sink" platform.


I used it quite a bit when I was in China for things other than messaging. Have to say it was a great experience, it works with literally EVERYTHING. You walk on the street - bam the bagger is using wechat QR code to ask for donation. A large number of normal people I encountered don't even use their wallets anymore - menu on wechat, mobile payment on wechat, taxi on wechat, utility on wechat. It's something that after using it, you know there's no way back.


WeChat is deeply integrated, the UI is excellent, it's fast and responsive even on low-end handsets. It's a 40MB APK that could well be the only app you need. WeChat is incredibly feature-dense, but it's also slick, efficient and highly usable. I don't like the monolithic app model, but WeChat have implemented it extraordinarily well.

Tencent are a phenomenal company that deserve far more respect in the west. The Chinese market may be distinctive, but WeChat's dominance of the Chinese market has come through innovation, clever design and good engineering.


We are discussing innovation and if you look at how much money change hands inside WeChat it is clear that it is getting ahead of whatsapp and facebook messenger by leaps and bounds.


Have you looked at Rust? It uses Option types, has generics, also uses return values for error handling but has a lot more syntactic sugar to make it cleaner than in Go.


I have tried Rust in the past, though not on this particular hobby project (my Clojure interpreter). I found it hard to get into, and I've gotten into a lot of languages in my time-- some of which are considered challenging (e.g. Haskell). With Rust, I always felt I spent too much time wrestling with it, and not enough time being productive. I imagine that you hit a threshold at some point and that begins to change. But for my side projects, that bar wasn't worth jumping.


Rust's major goals this year are around learnability and productivity; maybe come check it out again someday :)


Could you point to any materials (e.g. blog post, roadmap document...) that deal with this? Thanks.


https://blog.rust-lang.org/2017/07/05/Rust-Roadmap-Update.ht... is our "the year is half over" update, and has a link to the overall goals right at the top.


Awesome, thanks!


Inferred lifetimes? A man can hope :).


Inferring lifetimes from the implementation of a function won't happen for the same reason that inferring types won't happen: it is really nice for the signature of a function to not automatically be changed if the body is changed, instead programmers should be told when they might be breaking their users.

However, the compiler could (and did, I believe) run inference and suggest a fix that the programmer can explicitly include.


If it were always possible to infer all lifetimes, we'd do it. Unfortunately that's not the case.

There are a number of RFCs in the pipeline to help with lifetimes, including more elision. In no particular order:

https://github.com/rust-lang/rfcs/pull/2115

https://github.com/rust-lang/rfcs/pull/2094

https://github.com/rust-lang/rfcs/pull/2093


Rust's documentation is very well written. The authors have put in great effort to make things clear.

Granted Rust has some paradigms and constructs which are not easy to learn, I found it rather exciting. I think it has future scope.

Wonder whats happening with Redox. I hope Rust adds more libraries, especially network related, since the networked world is increasingly looking like a distributed OS of sort. Browsers are looking like an OS or a shell inside the OS. Browsers are getting more complex with more functionalities added every few months. Not sure I expressed my thoughts correctly, but I guess one can understand what I mean.

Rust should move away from C standard library, if possible.


> Wonder whats happening with Redox.

They've been involved in Google Summer of Code, and so have had lots of status update posts lately, here's the latest: https://redox-os.org/news/gsoc-self-hosting-final/

> Rust should move away from C standard library, if possible.

It's not always possible, but on systems where it is, there's some ability to do so, see https://github.com/japaric/steed


Thanks Steve.

>It's not always possible, but on systems where it is, there's some ability to do so, see https://github.com/japaric/steed

Doesn't linking to it make a Rust program "unsafe", in the Rust sense? Or my understanding is probably not correct.


Using unsafe inside of safe is totally fine. See https://doc.rust-lang.org/nomicon/safe-unsafe-meaning.html for more.


Cheers, thanks.


Huh, I had the opposite reaction. I thought that it was a very nice, clear article, which is phrased to be approachable by as many people as possible with some amount of technical background.

That technical background may not be as programmers. It may be power users, or web developers, or the like.

And I thought the analogies and illustrations helped out with giving some context that people who aren't systems developers might be missing.


The point is that when installing, you are not rebuilding. The hypothetical example here is for some kind of randomizaiton that applies, for instance, to the kernel during build time, such as randomization of structure layout. Having to rebuild every kernel you install to get a security patch, on every system you install it on, would be an enormous amount of time spent (there's a reason Gentoo is a fairly niche distro).

Such randomization can mitigate against certain kinds of attacks, especially making particular instances of an attack work differently between each kernel build, and thus increasing the difficulty of writing exploits that work across a broad range of kernel builds. There are about 30 different patch releases of the kernel for Debian Jessie alone; so such randomness, if applied across the different builds of a kernel within a release, across various different Debian releases, across different architectures, and also applied by other distros, can substantially increase the difficulty of writing an exploit that can affect a substantial fraction of Linux systems on the net.

That helps provide a form of "herd immunity", where the herd is all deployed Linux systems on the net. It doesn't provide any real protection for a particular build; so it's no harder to write an exploit that targets all system running the exact same kernel. But it does dramatically increase the difficulty of writing a widespread worm which relies on the given exploit, and which can easily spread between a variety of different systems.

Anyhow, that footnote was on a policy for explicit exceptions from the general policy. The general policy is that yes, builds should be reproducible, and any randomness should be generated locally. The footnote was giving a few example of potential exceptions which may be required, as a way of demonstrating that it would be fine to have the general requirement be reproducible builds with case-by-case, narrow exceptions for cases in which non-reproducible builds provide significant value.

And note that such exceptions may be based on how an upstream project operates. If the upstream kernel has some modules that build non-reproducibly in such a way, it may be more viable to encode an explicit exception to the policy for that case, than to remove that non-reproducibility.

It's important to keep in mind that someone applying a cleanup once accidentally removed almost all entropy from OpenSSL's random number generator on Debian (they even asked for review from upstream, and failed to get it, because of the confusing naming of upstream's mailing lists). Having an excessively rigid policy could mean that Debian maintainers would be forced to remove features that do provide some kind of benefit.


> Having to rebuild every kernel you install to get a security patch, on every system you install it on, would be an enormous amount of time spent

Rebuild? No. Just relink (and link in a just-generated binary containing the randomness seed). At boot time. Just what OpenBSD is experimenting with.


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

Search: