ned Productions Consulting


Technology musings by Niall Douglas
ned Productions Consulting
(an expert advice and services company based in Ireland)


Tuesday 19th September 2017 11.58am

Link shared: http://indeed.ie The contract market in C++ is so bad in Ireland right now that not one single contract in C++ is on indeed.ie (a jobs site aggregator) in the "new roles" section! I haven't seen it this bad since the depths of the financial crash :( Where are all the finance roles coming out of London through Brexit induced relocation? Or is it that Brexit uncertainty is sinking all boats?

Tuesday 12th September 2017 1.16am

Been making great use of my time without employment working on AFIO, my proposed low latency file i/o library for standardisation. I wrote a toy transactional key-value store with AFIO permitting up to 48 concurrent writers, and here is how it performs for 128 bit keys and 1Kb values with 1 thread: 1Kb values Windows with NTFS, no integrity, no durability, mmaps: Inserting 1M key-value pairs … Inserted at 518403 items per sec Retrieving 1M key-value pairs … Fetched at 2192982 items per sec 1Kb values Linux with ext4, no integrity, no durability, mmaps: Inserting 1M key-value pairs … Inserted at 695894 items per sec Retrieving 1M key-value pairs … Fetched at 5988023 items per sec To put those figures in context, LMDB which is considered one of the fastest key-value stores around achieves about 1.4 million fetches/sec with four threads.

Friday 11th August 2017 4.18am

You might remember that last year I spent lots of money on a MacBook Pro for one very specific reason: its NVMe SSD flash hard drive. Despite its supposed state-of-the-art performance, the various Windows benchmarking tools never really showed it to be particularly all that fast. Sure, with ridiculous queue depths and threads thrown at it then you could hit 3Gb/sec, but random 4Kb @ QD1 benchmarking always showed pretty poor results, maybe 2,500 IOPS (13Mb/sec) which is about a 400us average response time.

Friday 7th July 2017 3.30pm

My ZFS-on-Linux public facing server managed 289 days of trouble free uptime before today exhibiting massive i/o delay (see below) making it unusable without rebooting. That's the best it's ever achieved to date. Really shows how ZFS-on-Linux is becoming actually viable for reliable service provision, and as bug fixes land it's getting increasingly ever better. <br />top - 16:26:58 up 289 days, 23:27, 1 user, load average: 3.50, 2.19, 1.60<br />Tasks: 729 total, 1 running, 728 sleeping, 0 stopped, 0 zombie<br />%Cpu(s): 0.4 us, 0.8 sy, 0.0 ni, 86.5 id, 12.3 wa, 0.0 hi, 0.0 si, 0.0 st<br />KiB Mem: 16420640 total, 9778848 used, 6641792 free, 464 buffers<br />KiB Swap: 4194300 total, 0 used, 4194300 free.

Wednesday 7th June 2017 8.24am

Link shared: http://boost.2283326.n4.nabble.com/review-Outcome-Review-Report-tt4695267.html My proposed Boost.Outcome library's review report: http://boost.2283326.n4.nabble.com/review-Outcome-Review-Report-tt4695267.html. It was rejected after one of the lengthiest reviews in many years. Lots of good feedback on how it ought to look. #boostcpp #c++ #boost-outcome

Wednesday 7th June 2017 8.24am

Link shared: http://boost.2283326.n4.nabble.com/review-Outcome-Review-Report-tt4695267.html My proposed Boost.Outcome library's review report: http://boost.2283326.n4.nabble.com/review-Outcome-Review-Report-tt4695267.html. It was rejected after one of the lengthiest reviews in many years. Lots of good feedback on how it ought to look. #boostcpp #c++ #boost-outcome

Wednesday 7th June 2017 8.24am

Link shared: http://boost.2283326.n4.nabble.com/review-Outcome-Review-Report-tt4695267.html My proposed Boost.Outcome library's review report: http://boost.2283326.n4.nabble.com/review-Outcome-Review-Report-tt4695267.html. It was rejected after one of the lengthiest reviews in many years. Lots of good feedback on how it ought to look. #boostcpp #c++ #boost-outcome

Saturday 3rd June 2017 9.46pm

The peer review of my proposed Boost.Outcome library ended yesterday after being extended to two weeks to allow more discussion. Some 732 emails were sent on the topic, one of the most vigorous debates on boost-dev in many years, and a very highly productive one I think despite that we did not find consensus.

Saturday 3rd June 2017 9.45pm

The peer review of my proposed Boost.Outcome library ended yesterday after being extended to two weeks to allow more discussion. Some 732 emails were sent on the topic, one of the most vigorous debates on boost-dev in many years, and a very highly productive one I think despite that we did not find consensus.

Saturday 3rd June 2017 9.45pm

The peer review of my proposed Boost.Outcome library ended yesterday after being extended to two weeks to allow more discussion. Some 732 emails were sent on the topic, one of the most vigorous debates on boost-dev in many years, and a very highly productive one I think despite that we did not find consensus.

Archive