Skip to main content

Moore's Law and the Chromebook

Moore's Law as summarized:
"Moore's law" is the observation that the number of transistors in a dense integrated circuit has doubled approximately every two years.  ... and projected this rate of growth would continue for at least another decade. (wikipedia)
I find it hard to believe that Moore's Law was more of a project or marketing plan than engineering prediction. Not that doubling transistor count is an easy feat but it's more Economics. For all we know Intel might have had the capability to quadruple transistor density, however, the cost would have kept the chips too high effecting the economics. 

I recall using the Dec Alpha in the same form factor as the PC. They were screamers. I presume it was part manufacturing, part density, and mostly it's mainframe/mini heritage. Sadly, the Alpha was acquired and then discarded.

In the meantime we continue to see a number of chip vendors that are working on chips that are "good enough". ARM and Rock. We also see a number of vendors, possibly taking lessons from one laptop per child and manufacturing Chromebook, Chromebox, Chromebase and Chromebit. For all but the most premium devices all of these machines are relegated to using older or commodity chips, memory and SSD.

While the PC and MAC markets are running wild on the tip of the price spear with the latest chips the ChromeOS hardware market is simply consuming the cast offs. Eventually the ChromeOS market is going to fracture under the stress. PC and MAC manufacturers want to preserve their margins. ChromeOS manufacturers are going to see premium brands enter the market with a need to better margins and then soon enough the pirates are going to enter and try to capture the bottom of the market. (we already see Intel/Microsoft entering into the stick computer and now Microsoft is working on the CloudComputer)

And the exceptions or indicators:
  • HP Stream (appears to be positioned as an RDP console)
  • EeBook (FAIL)
  • in general netbooks (FAIL)
  • RockChip (link) described as SoC based on the ARM processor
  • Apple buys chip manufacturer (link)
  • look at the number school systems that are purchasing ChromeOS based devices
BTW: I'm not touching the OS war here although I have a very strong opinion.

Comments

Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: http://www.eeti.com.tw/drivers_Linux.html (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the setup.sh answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…