It's not hypocracy if her position is consistantly that the elite and rich defense contractors (doesn't her husband own much of URS) are above the law, and everyone else must bow before them.
Her legislation could say "only senators, former senators, people with over $100 million, and defense contractors can use drones to spy on others" -- and it wouldn't be hypocracy. It'd just be evil.
Another guy'll be making a robot painting system that aims it's cars "so make a more profitable assembly line".
Yet another'll make a self-driving car "so you won't have to worry about drunk drivers anymore".
Once those pieces are all there (hint, today), it doesn't take much for the last guy to glue the 3 together; hand it a gun instead of spraypaint; and load it with a databases of faces you don't like.
enterprise
Seems backwards.
In our work ("Enterprise") setting, we have RAID-Z that does plenty of checksumming to survive failures; so we'd want the extra performance (the only reason where our work uses SSDs instead of spinning disks).
In a consumer setting; where people store precious irreplacable memories (pics of kids) and their ownly copy of financial data; it seems reliability should rule.
performance
The biggest opportunity for GPUs in Databases isn't for "performance". As others pointed out - for performance it's easier to just throw money at the problem.
GPU powered databases do show promise for performance/Watt.
However, energy efficiency is not enough, energy proportionality is needed. The objective of this work is to create an entire platform that allows execution of GPU operators in an energy proportional DBMS, WattBD, and also a GPU Sort operator to prove that this new platform works. A different approach to integrate the GPU into the database has been used. Existing solutions to this problem aims to optimize specific areas of the DBMS, or provides extensions to the SQL language to specify GPU operation, thus, lacking flexibility to optimize all database operations, or provide transparency of the GPU execution to the user. This framework differs from existing strategies manipulating the creation and insertion of GPU operators directly into the query plan tree, allowing a more flexible and transparent framework to integrate new GPU-enabled operators. Results show that it was possible to easily develop a GPU sort operator with this framework. We believe that this framework will allow a new approach to integrate GPUs into existing databases, and therefore achieve more energy efficient DBMS.
Also note that you can write PostgreSQL stored procedures in OpenCL - which may be useful if you're doing something CPU intensive like storing images in a database and doing OCR or facial recognition on them: http://wiki.postgresql.org/images/6/65/Pgopencl.pdf
Introducing PgOpenCL - A New PostgreSQL Procedural Language Unlocking the Power of the GPU
you so long as the information about you is perceived to have value.
The tricky part people are overlooking is value to whom?
Which basically means as long as you live,
Disagree - it basically means the information will be kept forever in certain silos. The NSA will probably keep your information forever - so 999 years ago of your descendants are suspected of something controversial then they can use what you post on
But these will all be in private silos of data. The public internet will probably forget you much much much faster.
Interesting and sad.
Those links would probably also be great for NSA & Google like data mining to monitize those users too.
DB: Queries with Bounded Errors and Bounded Response Times on Very Large Data
The majority of CPU cycles in data centers is going to be looking up and filtering specific records in database
Approximate Computing is especially interesting in databases. One of the coolest projects in this space is Berkeley AMPLab's BlinkDB. Their cannonical example
SELECT avg(sessionTime) FROM Table WHERE city='San Francisco' ERROR 0.1 CONFIDENCE 95%
should give you a good idea of how/why it's useful.
Their bencmarks show that Approximate Computing to 1% error is about 100X faster than Hive on Hadoop.
Razer forces you to create an account with them before you can use the software with the mouse. You cant configure the mouse in any way until you make an account with them and activate your computer and account through their server. If they decide to take down their activation server for any reason, you will never be able to use the software. If you live somewhere without access to internet, you will not be able to activate and use the software. If you work somewhere that has a network behind firewalls, chances are even though you can download the Synapse software, the firewall may also block you from activating and using the software as well. If your connection drops out for any reason, the Synapse software will make a habbit of locking up on you while it transitions to offline mode. During that time your settings may revert or possibly not be saved.
I'll bet Julian Assage
Why do so many forums (/., reddit) have so many Assage bashers even under articles that aren't about him.
Back when he was best known as being a postgres contributor, he seemed like a very normal nice guy.
It's not his fault that he claims big organizations are out to get him - because big organizations really are out to get him.
"You don't go out and kick a mad dog. If you have a mad dog with rabies, you take a gun and shoot him." -- Pat Robertson, TV Evangelist, about Muammar Kadhafy
