mkarlsch

I can only second this. The placeholder in the search bar is “ex: tacos, breakfast, …” so I searched for tacos - zero results. Having a bit more content would likely leave a better first impression.

remerge | (Senior) Software Engineer | Full-time | Berlin,Germany | Remote (within +/- 3h CET) or On-Site | https://www.remerge.io

We help app businesses to grow.

Our stack: Go, Kafka, Druid, Bigquery, ElasticSearch, Python+Tensorflow, Ruby/Rails, Typescript+React, lots of GCP services, Ansible + Terraform.

You would help us in designing, building, improving and operating services that process several trillion event per - coming with an "interesting technical challenges included" guarantee.

At remerge we put culture and people first:

- we are fully transparent (from salaries to company financials)

- clear role design and a growth framework - so you know where you stand, what's next and how to get there

- our renumeration includes share options, an education budget and a percentage of the company profit as end of year bonus

- unlimited vacation days (with a minimum you have to take) + "fully covered one month work from any office" program

- work from home/remote support (setup + internet reimbursement)

Apply at:

- https://www.remerge.io/careers/5106614003 (backend)

- https://www.remerge.io/careers/4953590003 (frontend)

- https://www.remerge.io/careers/4956657003 (machine learning)

- https://www.remerge.io/careers/4964502003 (VP Engineering)

We used Apache Drill a few years back and it could do exactly that - run locally and provide a SQL interface to query parquet files. Still great to see more and better options!

Indeed. Thanks for the hint! While the allocations are still 2.5x, not by accident calling into easyjson makes goccy/go-json perform faster than easyjson with generated code by ~10%. That is some impressive result.

That looks great, especially some of the unique optimisations. I gave it a nonscientific test run with a set of 1k different 2-4kb JSON encoded messages that we saw in our day to day traffic using the default Go benchmark library. Compared to easyjson (generated parser) goccy/go-json is unfortunately 20-25% slower and allocated four times the number of bytes.

Any chance that you will implement code generation like easyjson?

Agree! Both reports are a pretty good and reflect the status quo in the industry. There is an overcollection and oversharing of data without proper consent and that has to stop. For Europe - forcing the ad-tech industry to adhere to the GDPR is the correct next step as self regulation did not work.

Having said that the report paints a pretty dark and one-sided picture. Let's see how far the authorities will follow their argumentation / conclusion.

(full disclosure: I work in that industry.)

Interesting project, however it looks like the last commit is from September 2017 so either it is just very stable or not maintained anymore?

Same here - we don’t use channels in the hot code path and did replace the Go HTTP parser.

Between 2-40KB, the average is likely closer to 2-4KB (Gzipped JSON or Protobuf)

We wrote our bidder (in app advertising) in Go. It is globally distributed (close to the exchanges) and handles 1.5-2M requests/s (OpenRTB,~50-90k/s per instance) with a p99 of 10-20ms (without network latency). Really happy with Go, especially the GC improvements done by the Go team in the last few releases. For a previous similar project we used Ruby which was quite a bit slower.

Was already there but disabled due to https://github.com/golang/go/issues/18190#issuecomment-26525...