Similarly, if not performance-focused, I can wholeheartedly recommend Building Git[0], which walks you through building your own git clone in Ruby (although the language is immaterial).
149 karma · joined January 1, 2014
(I'm not a Rust expert and I'm on my phone though, so I might be missing something.)
This approach is a smart way to get the same precision as the kernel without tying it to the vDSO implementation as in the post, so presumably someone at Google was worried about very similar issues. I also considered an implicit automatic refresh, but ultimately for my purposes controlling when to take the hit was more important than the slight increase in API complexity introduced by an explicit call.
In my benchmarks RDTSCP has a slight advantage, despite the slower latency on paper, because it doesn't fully serialise the instruction stream (later instructions can start executing, unlike with LFENCE). Whether the ECX clobber will outweigh that will depend on the situation.
In this case distributed tracing absolutely was the right choice. These were not simple computational tasks. The components were highly stateful and interconnected both on- and cross-host. Between this and the timescale, as well as the volume of events and the dollar-value impact of each potential failure (of which there were many), we needed real-time analysis capabilities, not a profiler.
>It all seems very brittle, though. And that something has gone very wrong with our ecosystem of tools, languages, and processes when it becomes advisable to massage source until specific passes in a specific version LLVM don't mess things up for other passes.
I would say the main takeaway is actually to not do that, precisely because it's brittle, difficult to understand, and can backfire by making things harder for the compiler. As I point out at the end, the vast majority of developers will be better served by sticking to common idioms and making their intent as clear as possible using language facilities, rather than trying to outsmart the compiler or, conversely, relying excessively on the optimiser as a magic black box.
That being said, I do find it helpful to understand the broad strokes of the optimisation pipeline (things like "callees are optimised before callers", "maintaining invariants enables more simplifications", or "early simplifications are better") to make the most of it. Like with any other tool, mastery means letting it do its job most of the time but knowing when and where to step in if necessary.
Unfortunately there's also still no agreement on what 5G will actually be, what technologies it will entail, or how it will be deployed. Of course, since none of this is defined yet, there are also no guarantees on what performance will be achievable in practice.
The industry will need to solve this issue long before 5G is widespread. The solution will likely involve DSRC, C-V2X, or LTE-V/LTE Direct, which are tailored for the vehicular communication use case (involving both vehicle-to-vehicle [V2V] and vehicle-to-infrastructure [V2I]). It's unlikely a single technology will be able to handle all the challenges of a V2X scenario (highly mobile nodes, congestion, low SNR, requirements for sub-millisecond connection times), and so a second connection management layer will have to be built on top of multiple existing PHYs to enable simultaneous low-latency, high-throughput, and secure communications.
(Note that the linked article is actually about in-vehicle communication, however.)
Use "-C -" to tell curl to automatically find out where/how to resume the transfer. It then uses the given output/input files to figure that out.
We are looking to fill several openings across Engineering, Sales, and Management: https://veniam.com/jobs/. We have opportunities for cloud, analytics, front-end, hardware design, and embedded software work.
Veniam is building the Internet of Moving Things by turning vehicles into WiFi hotspots and building networks of connected vehicles that expand wireless coverage and collect terabytes of urban data for smart city applications.
As a member of our team at Veniam, you will have the opportunity to work in fast moving teams of 3-5 people, work closely with our Customer Success teams and often directly with key customers worldwide. We are organized in changing mission-driven teams that deliver continuously and you will have the opportunity to work on something new every few weeks.
If you're interested drop me a line at hcabral@veniam.com!
(Disclaimer: I work for the company who implemented that network.)
Veniam just raised a $4.9M series A to build the networking fabric for the Internet of Moving Things (http://techcrunch.com/2014/12/02/veniam-picks-up-4-9m-to-tur...), and we are looking for a Full-Stack Software Engineer to help us.
Someone with entrepreneurial spirit who is different, drives change and shares our passion for developing cutting-edge products that people and businesses love and use everyday.
Critical thinking, deliberate problem solving, disruptive mindset, and excellent communication are essential qualities, as you will be working in an exceptionally talented team with know-how across different disciplines, constant learning, boundless creativity, and outstanding execution – always in tandem with our headquarters in Silicon Valley.
If this is you, please share your CV with us at jobs@veniam.com
Target skills:
* Node.js
* MySQL
* MongoDB & Redis
* Computer Networks (!)
* AWS
* and excellent English.
Veniam just raised a $4.9M series A to build the networking fabric for the Internet of Moving Things (http://techcrunch.com/2014/12/02/veniam-picks-up-4-9m-to-tur...), and we are looking for a Full-Stack Software Engineer to help us.
Someone with entrepreneurial spirit who is different, drives change and shares our passion for developing cutting-edge products that people and businesses love and use everyday.
Critical thinking, deliberate problem solving, disruptive mindset, and excellent communication are essential qualities, as you will be working in an exceptionally talented team with know-how across different disciplines, constant learning, boundless creativity, and outstanding execution – always in tandem with our headquarters in Silicon Valley.
If this is you, please share your CV with us at jobs@veniam.com
Target skills:
* Node.js
* MySQL
* MongoDB & Redis
* Computer Networks (!)
* AWS
* and excellent English.
We are looking for a Full-Stack Software Engineer to help us build the networking fabric for the Internet of Moving Things.
Someone with entrepreneurial spirit who is different, drives change and shares our passion for developing cutting-edge products that people and businesses love and use everyday.
Critical thinking, deliberate problem solving, disruptive mindset, and excellent communication are essential qualities, as you will be working in an exceptionally talented team with know-how across different disciplines, constant learning, boundless creativity, and outstanding execution – always in tandem with our headquarters in Silicon Valley.
If this is you, please share your CV with us at jobs@veniam.com
Target skills:
* Node.js
* MySQL
* MongoDB & Redis
* Computer Networks (!)
* AWS
* and excellent English.
Message body
just as in <subject> use imperative, present tense: “change” not “changed” nor “changes”
It's true that smaller vendors like Lattice seldom provide Linux software, but it's also rare to find bigger shops (as opposed to hobbyists) who don't use Xilinx or Altera exclusively, and Linux at that.
[0] Lawyers, on the other hand, undergo very extensive examination, and they can only practice law if they are members of the Ordem.
We had a bug of the kind once, where a Microblaze core would fail to boot the Linux image after what seemed a trivial modification in the peripheral code, but it turns out we were packing the logic so tightly that this change blew the timing on some critical net. Ah, the joys of digital design.