HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
treo
benchmarking_nd4j
Java2018–2018
treo / benchmarking_nd4j

benchmarking_nd4j

Simple Microbenchmarks for ND4J utilizing the JMH

2Distinct people
2Mentions
0Explicit recommenders
0GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Simple Microbenchmarks for ND4J utilizing the JMH

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2018-06-22 20:44:50 UTC to 2018-06-23 07:21:57 UTC.

012018-06-22 20:00:00 UTC to 2018-06-22 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 22, 20:002018-06-22 21:00:00 UTC to 2018-06-22 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-06-22 22:00:00 UTC to 2018-06-22 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-06-22 23:00:00 UTC to 2018-06-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-06-23 00:00:00 UTC to 2018-06-23 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-06-23 01:00:00 UTC to 2018-06-23 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 23, 01:002018-06-23 02:00:00 UTC to 2018-06-23 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-06-23 03:00:00 UTC to 2018-06-23 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-06-23 04:00:00 UTC to 2018-06-23 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-06-23 05:00:00 UTC to 2018-06-23 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-06-23 06:00:00 UTC to 2018-06-23 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-06-23 07:00:00 UTC to 2018-06-23 08:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 23, 07:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jun 22, 20:002018-06-22 20:00:00 UTC2018-06-22 21:00:00 UTC101
Jun 22, 21:002018-06-22 21:00:00 UTC2018-06-22 22:00:00 UTC000
Jun 22, 22:002018-06-22 22:00:00 UTC2018-06-22 23:00:00 UTC000
Jun 22, 23:002018-06-22 23:00:00 UTC2018-06-23 00:00:00 UTC000
Jun 23, 00:002018-06-23 00:00:00 UTC2018-06-23 01:00:00 UTC000
Jun 23, 01:002018-06-23 01:00:00 UTC2018-06-23 02:00:00 UTC000
Jun 23, 02:002018-06-23 02:00:00 UTC2018-06-23 03:00:00 UTC000
Jun 23, 03:002018-06-23 03:00:00 UTC2018-06-23 04:00:00 UTC000
Jun 23, 04:002018-06-23 04:00:00 UTC2018-06-23 05:00:00 UTC000
Jun 23, 05:002018-06-23 05:00:00 UTC2018-06-23 06:00:00 UTC000
Jun 23, 06:002018-06-23 06:00:00 UTC2018-06-23 07:00:00 UTC000
Jun 23, 07:002018-06-23 07:00:00 UTC2018-06-23 08:00:00 UTC101

What Hacker News says

2 sources
It looks like while converting from my benchmarking code you've dropped the 'f' when creating the resulting array. https://github.com/treo/benchmarking_nd4j/blob/master/src/ma... The difference is rather huge with the newer versions of nd4j. While the numbers in the following gists do not contain the measurements I took for neanderthal, they do contain the numbers that I got for ND4J. Without f ordering: https://gist.github.com/treo/1fab39f213da26255cf4f75e383ff90... With f ordering: https://gist.github.com/treo/94fe92c9417b5c8b24baa12924a35b0... As you can see something happened in the time between the 0.4 release (I took that as the comparison point since that was when I ran my own benchmarks the last time) and the 0.9.1 release that introduced additional overhead. Originally I planned to create my own write-up on this, but I wanted to
Read the rest
first to find out what happened there. Given that ND4J is mainly used inside of DL4J and the matrix sizes it is used with usually are rather large, the performance overhead difference that I've observed there for tiny multiplications isn't necessarily that bad, as the newer version performs much better on larger matrices.
In Neanderthal vs. ND4J – Native Performance, Java and CPU

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.