News for hackers. Stuff that matters.
Re:DNS over HTTPS by metafunctor on Wednesday January 17, 2018 @04:34AM (#16166648)
Can anyone give examples of cases where “performant” would be better than “efficient”?

To my mind, the difference is that “performant” delivers results quickly, whereas “efficient” uses little energy. A performant solution might be efficient, but not necessarily, and vice versa. Does anyone else share this understanding or am I living in a linguistic bubble?

Not sure about Swedish (Daniel is Swedish), but in Finnish, we have the word “suorituskykyinen”, meaning “efficient” or “able to perform”. I can see how Finnish writers might want to use “performant” to replace this commonly used word. Perhaps there's a similar history for Swedish speakers? I sure have seen “performant” a lot in academic texts written by Finnish and Swedish speakers in the last 20 years.

Re:DNS over HTTPS by barrkel on Wednesday January 17, 2018 @04:51AM (#16166715)

    efficiency = performance / resources
Efficient has connotations of economy, of optimal use of resources but with a hint of parsimony - another way to get efficiency is to reduce the denominator.

Performant emphasises the numerator much more.

Re:DNS over HTTPS by da_chicken on Wednesday January 17, 2018 @10:44AM (#16168794)
Yep. A top fuel dragster goes from 0-60 mph (~0-100 kmh) in about 0.2 seconds, but it will use about 20 gallons (~75 liters) of fuel going 1,000 ft (~300 m). Very high performance. Very low efficiency.
Re:DNS over HTTPS by jgoldfar on Wednesday January 17, 2018 @07:24AM (#16167310)
*increase the denominator.

nitpick aside, agreed

Re:DNS over HTTPS by da_chicken on Wednesday January 17, 2018 @10:31AM (#16168678)
The denominator is "resources," which here means "resource cost." Increasing resource cost reduces efficiency. You want to either increase the numerator ("performance") or decrease the denominator ("resources").
Re:DNS over HTTPS by barrkel on Wednesday January 17, 2018 @09:16AM (#16168014)
Reducing the denominator is the other way to increase efficiency. The denominator is the number under the line, the divisor.
Re:DNS over HTTPS by kodablah on Wednesday January 17, 2018 @04:39AM (#16166667)
"My mining algorithm, which uses a lot more CPU and memory, is more performant." The key being that performant is often associated w/ speed (i.e. higher performing) whereas efficient ambiguously can refer to many things you have improved on.
Re:DNS over HTTPS by metafunctor on Wednesday January 17, 2018 @04:44AM (#16166683)
Yep, that's how I understand the word “performant” as well. A car that accelerates from 0-100 kph in under 3 seconds would be ”performant”. A car is “efficient” if it burns less than 4 liters of gasoline per 100 kilometers.
Re:DNS over HTTPS by vectorEQ on Wednesday January 17, 2018 @04:47AM (#16166702)
'performs more [efficiently|accuratley]' would be proper english (not that i speak it well.... :D).

webster says:

"performant"

The word you've entered isn't in the dictionary. Click on a spelling suggestion below or try again using the search bar above.

    preformant performance performing performances performable preformants perforate conformant perform formant performed informant performer perforata performers performs preformat
Re:DNS over HTTPS by barrkel on Wednesday January 17, 2018 @04:53AM (#16166721)
The algorithm doesn't perform more efficiently or accurately, though - it's less efficient (it uses more resources) and it should be the same accuracy (or we're comparing apples with oranges).
Re:DNS over HTTPS by vectorEQ on Wednesday January 17, 2018 @05:01AM (#16166766)
haha yah i know, it would perform terrible. imagine running a big dns server at ISP level, and having to perform 9 million tls handshakes a second. have fun with that lol. this was just an example of how to avoid the 'performant' word.
Re:DNS over HTTPS by seandavidfisher on Wednesday January 17, 2018 @08:56AM (#16167862)
If we’re getting pedantic about linguistics, wouldn’t that be, “it would perform terribly” instead of “it would perform terrible”?
Re:DNS over HTTPS by mohamedattahri on Wednesday January 17, 2018 @06:12AM (#16167014)
In my understanding, performance is based on the value of a measure improving in one way or another.

Efficiency is relative to the amount of resources required to achieve a similar result. To use the car example above, a car that can do 100km/h at 4L/100km is more efficient than another can than do 100km/h at 8L/100km.

The point of absolute efficiency is referred to as optimum. Essentially, top performance possible with the minimum of resources possible.

Re:DNS over HTTPS by Angostura on Wednesday January 17, 2018 @07:54AM (#16167486)
I think the word that was being grasped for is 'faster'.

It suffers in that doesn't sound very technical.

Re:DNS over HTTPS by v_lisivka on Wednesday January 17, 2018 @08:42AM (#16167776)
GPU can perform more operations than CPU, but GPU is slower than CPU, not faster.
Re:DNS over HTTPS by greiskul on Wednesday January 17, 2018 @04:10PM (#16171862)
Yes, throughput vs latency is a very important distinction. An airplane is always faster then a train, but if what you are measuring is throughput, a train can be more performant. It depends on the context, but that's fine. There is no such thing as a made-up word if the word has a meaning, and is regularly used by a group of people.
Re:DNS over HTTPS by Angostura on Thursday January 18, 2018 @09:49AM (#16177411)
So is the GPU more or less 'performant?'

That's right - the CPU is faster at completing the job, though the GPU executes instructions more quickly.