Power Wastage on an Idle Laptop
randomascii.wordpress.com
randomascii.wordpress.com
Is a general overview. Intel graphics cards almost never enter the lowest idle state in Linux, last time I checked.
Can somebody tell the Dropbox developers that right after boot is the exact wrong time to kill disk performance with a massive number of very random, very short reads? Jesus. People want to use their newly booted PC, not wait for Dropbox to realize nothing has changed after all while it chokes the browser being started.
I figure they don't notice because they have two PCIE 512GB SSD disks in a raid0 in their dev boxes. They need to test this stuff with spinning rust.
And I tell them, "Exactly. If I make my app run well on this laptop, I know for sure it will run acceptably on every machine here."
http://www.theverge.com/2015/10/28/9625062/facebook-2g-tuesd...
Pretty handy for testing. I've used it to simulate a bad uplink in between a dslam and bras.
https://www.excentis.com/blog/use-linux-traffic-control-impa...
The title of this post would read just as well as "Power Waste on an Idle Laptop".
I also see "Usage" quite a lot on GitHub Readme pages, where I think "Use" would suffice.
Many words seem to be shortened for common use. E.g. Photograph to photo.
Why extend the length of other words?
Of the six potential uses, I think this one is most relevant:
"Forming nouns indicating a process, action or result. E.g. blockage, slippage, shrinkage"
Yet in this case the extension to "wastage" still feels somehow redundant. For example, I wouldn't say "Household wastage in modern society".
http://www.ourcivilisation.com/smartboard/shop/gowerse/abc/w...
I guess in this case I would read "wastage" as the reduction of available power over time. That is, the power was wasting away. Rather than the "waste" of power (frivolous use) by too many CPU cycles.
Anyway, English, wonderful language.....
Traditional Unix 'man(1)' pages are against you.
(And those were by the famously concise /usr, /bin and 'creat()' guys, though that last one was later regretted in a moment of weakness ;-)
"Bryan: [...] But what I do have are a very particular set of skills, skills I have acquired over a very long career. Skills that make me a nightmare for people like you. If you let my daughter go now, that'll be the end of it. I will not look for you, I will not pursue you. But if you don't, I will look for you, I will find you, and I will kill you."
I don't speak any german, but I have a pretty good idea of what that means.
http://www.imdb.com/title/tt0936501/releaseinfo#akas
The worst localized title I know is "Die Hard: With a Vengeance", mysterious called (literally) "Die Hard - Mega Hard" in Denmark. Schwarzenegger's "Red Heat" is (translated) "A Russian cleans up Chicago".
My understanding was that this shouldn't be true since Windows 7 (and on Mac, since Mavericks): https://en.wikipedia.org/wiki/Timer_coalescing
I suspect very few programs are using SetCoalescableTimer, but I'll add that as a suggestion.
Also includes some info about driver/firmware limitations, wake up sources, supported power states etc.
(To the downvoters: I would love to hear feedback about why I'm mistaken here. Windows 7 didn't need such an authoritarian defender (auto-deleting things, scanning, etc.) and it felt just as safe)
But, VS installed and started sqlservr on millions of developer machines so they should have paid some attention to this issue. Super sloppy.
You don't need to install SQL Server Express, just pay a bit more attention to what you're installing.
If so, why? Why shouldn't it just behave reasonably? Computers should be our slaves.
Users don't understand that computer resources like CPU time and battery level are really their property. It is an awful like paying a hidden poor quality tax.
It is not unreasonable to expect software to not waste CPU and battery time.
https://en.wikipedia.org/wiki/Development_of_Windows_Vista and https://en.wikipedia.org/wiki/WinFS
I'm genuinely curious what your source is for this. From the following uncited text on Wikipedia?
"An early revision of WinFS was also included, but very little in the way of a user interface was included, and as such it appeared to early testers to be nothing more than a service that consumed large amounts of memory and processor time."
Or do you have another source?
WinFS betas were released post-Longhorn as well.
http://serverfault.com/questions/94212/does-cpu-power-manage...
The really questionable thing is automatically installing it along with Visual Studio.
It's only showing you Applications from the last 8 hours by default.
In 10.9 it was a simple function of on-CPU time and wakeups with each wakeup counted as 500µs of CPU time, in 10.10 a bunch of new counters were added (with machine-specific conversions to CPU time estimates) variables were added to the mix: whether the process was in "background" QoS, the number of disk read/writes, GPU usage and network activity (in packets#)