People using this feature freak me out when I'm riding my motorcycle into San Francisco. The normal behavior of phone-users is to brake, speed up, slow down, bounce off of the lane markers (Driving by Braille) and generally endanger those of us on two wheels.
Tesla drivers? There they are, tapping away on the fucking phone with their eyes down and the car is gliding along, centered in the lane and steady, station-keeping a safe distance form the car in front of it.
Please, more like this.
As far as people blaming cars for their own stupidity, I'll trust the engineers at Tesla, thanks. Our Audi 5000 didn't take off by itself and neither do Teslas.
My Audi 5000 always got the accelerator stuck under those horrible floor mats. I eventually got tired of fixing the floor mats and just took them out to be safer. About 2 months later, the throttle itself got stuck. I shut that boat of a wagon off but lost the brake booster support to slow it down. I pulled the e-brake and the e-brake cable snapped, so I had to perform a few "evasive maneuvers" to get it safely into a parking lot and stopped.
It's not a matter of downloading the emails... it's a matter of making sure he has valid logins to every site he's using and that he can change his email on each site to a new one in that time.
I know it would take me close to 30 days to change my profile on every site i've created a login on in the last 20+ years...Most of them have email confirmation when you change your address. Not to mention requiring email for password resets.
I had a flip star-tac with the extended battery, that thing would last almost 3 weeks on a charge if you didn't talk much... was the most amazing stand-by, emergency phone ever.
It's designed to reduce the number of inputs a driver/pilot have to make... it is not designed to be used in zero visibility and still requires the driver/pilot to be aware of what is going on and be ready to take control.
Not sure how their DBW system is setup, but even in my old 2004 Subaru, the DBW system uses two sensors and duplicate wiring.
There are two potentiometers in the throttle pedal and in the throttle body. A change in pedal voltage, reflects as a change in throttle body stepper motor voltage = open throttle body (to some percentage equal to the pedal movement).
If the two potentiometers are off by more than 0.05v, then the ECU shuts off the input from the pedal and the car goes into limp-mode where it won't open the throttle plate more than a few deg and won't let the car accelerate any faster than idle.
There were things so sensitive in her email that the DoJ Inspector General investigating initially lacked a high enough clearance to read some of the content.
You don't really seem to understand how clearances work... there's no high or low clearance... Access is based on need to know only. There are different programs that you can be briefed into depending on that need to know, but there aren't really levels of clearance beyond the standard secret/top secret just many compartments within secret or top secret.
Fusion-io did that 5 years ago with their pci-e flash cards. The drives were very vocal about any trauma they might have suffered and would drop into a reduced write mode if you didn't heed the warnings in order to get your attention... if you still ignored them, they would go read only and you'd be forced to copy your data off.
SanDisk's Infiniflash is 512TB in a 3U chassis that is SAS-connected. You can front this with something like DataCore's SANsymphony to turn it into a NAS/SAN appliance.
The pricing looks to be around $1/GB, which is a ton cheaper than building a SAN of that capacity, plus it's much smaller in power/space/cooling.
Aah, managed to download this plugin and get it working. It connects to a different server than chat.facebook.com as well.
I've noticed in the comments that some folks can still use xmpp with chat.facebook.com, but whatever local server that DNS is pointing me at is no longer accepting connections.
Pretty much all of them as we move into 3D NAND... I know samsung has one out already as the 850 EVO... everyone should be right behind them with similar products.
Newer 3D NAND is using a charge trap design which basically solves the electron leakage issue found with the older floating gate NAND...
Also, the move to the newer 3D NAND brings us back up to 40nm processes vs the 10nm gates we are currently working with, allowing for much better reliability.
Disclaimer: I've been selling enterprise flash storage for the last 6 years.
You can't read game files faster because the process that reads the game file is single threaded vs multi-threaded... so it can only read as fast as a single thread can read.
A fully saturated CPU has enough lanes to do about 26-28GB/sec, but a single I/O thread might only be able to do 100-200MB/sec.
There was never any reason in the OS before today to make that any faster because the spinning disks that fed data to the CPUs couldn't do more than 100MB/sec.
Now that we have all this great flash, code needs to be re-written to be able to use other idle CPU time to spin up more threads and read the data faster.
It's worth remembering that 98k IOPS will be at a very small block size and will rapidly drop as you increase block size to 4K-1MB as the larger transfer size will directly equate to less I/O.
The real problem is that apps are not written for multi-threaded I/O which is what you really need in order to take advantage of the throughput provided by PCI-e flash.
Booting from RAID is more supported, and the support is baked into nearly every BIOS out there... booting PCI-e over NVMe or UEFI is brand new and very few things support it and all the code is new.
Booting through a raid card that has it's own BIOS is nothing like booting off of a native PCI-e device.
Booting from pci-e uses either a UEFI driver or NVMe today, two technologies that are kinda in their infancy.
The code is not yet fully optimized/etc and you may see reduced speeds at least until you can get into an OS layer and load up a more feature-full driver.
The PCI-e native SSDs are indeed faster, the problem is, the code reading data off of them (your application/os) isn't written to take advantage of the increased speeds. Single threaded reads cap out at the read speed of a single thread, and that isn't that fast. This is especially true if they are 4K reads vs 1M reads, as you aren't going to saturate anything until you get up into larger read sizes.
To really take advantage of the bandwidth SSDs enable, you need to be running multiple parallel apps running multiple reads, or you need an app that can do multi-threaded reads.
This is because you get stuck leaving the CPU to handle all the context switching between virtual block storage in DRAM and memory. The CPU has to copy data out of block and into memory before it can actually use it, so by making a ram disk you end up giving the CPU 2-4x the amount of work to do for what should be a DMA read/write, which would normally be offloaded.
Also, your reads from your game are going to be single-threaded, and a single read/write thread is going to be pretty slow.
Slashdot Mirror
Steel beams and all...
People using this feature freak me out when I'm riding my motorcycle into San Francisco. The normal behavior of phone-users is to brake, speed up, slow down, bounce off of the lane markers (Driving by Braille) and generally endanger those of us on two wheels.
Tesla drivers? There they are, tapping away on the fucking phone with their eyes down and the car is gliding along, centered in the lane and steady, station-keeping a safe distance form the car in front of it.
Please, more like this.
As far as people blaming cars for their own stupidity, I'll trust the engineers at Tesla, thanks. Our Audi 5000 didn't take off by itself and neither do Teslas.
My Audi 5000 always got the accelerator stuck under those horrible floor mats. I eventually got tired of fixing the floor mats and just took them out to be safer. About 2 months later, the throttle itself got stuck. I shut that boat of a wagon off but lost the brake booster support to slow it down. I pulled the e-brake and the e-brake cable snapped, so I had to perform a few "evasive maneuvers" to get it safely into a parking lot and stopped.
It's not a matter of downloading the emails... it's a matter of making sure he has valid logins to every site he's using and that he can change his email on each site to a new one in that time.
I know it would take me close to 30 days to change my profile on every site i've created a login on in the last 20+ years...Most of them have email confirmation when you change your address. Not to mention requiring email for password resets.
I had a flip star-tac with the extended battery, that thing would last almost 3 weeks on a charge if you didn't talk much... was the most amazing stand-by, emergency phone ever.
Eh, keeping NAND cool isn't really an issue. NAND likes heat. It's the controllers that you have to keep cool.
Source: I just spent the last 6 years working for Fusion-io/SanDisk
....Autonomous pilot.
It's designed to reduce the number of inputs a driver/pilot have to make... it is not designed to be used in zero visibility and still requires the driver/pilot to be aware of what is going on and be ready to take control.
Not sure how their DBW system is setup, but even in my old 2004 Subaru, the DBW system uses two sensors and duplicate wiring.
There are two potentiometers in the throttle pedal and in the throttle body. A change in pedal voltage, reflects as a change in throttle body stepper motor voltage = open throttle body (to some percentage equal to the pedal movement).
If the two potentiometers are off by more than 0.05v, then the ECU shuts off the input from the pedal and the car goes into limp-mode where it won't open the throttle plate more than a few deg and won't let the car accelerate any faster than idle.
... on my Samsung S5, full brightness in 12Noon sun is quite usable... never had an issue.
Who are you calling old?
... to virtual sex online... This is what computers were made for.
They just need a 2-column setup.... current posts on one side, or one pane, and "important"/interesting posts in the other.
Plenty of space for it in the main twitter web page, mobile people may have to swipe left or right between screens... Tweetdeck could do it simply...
Fusion-io did that 5 years ago with their pci-e flash cards. The drives were very vocal about any trauma they might have suffered and would drop into a reduced write mode if you didn't heed the warnings in order to get your attention... if you still ignored them, they would go read only and you'd be forced to copy your data off.
SanDisk's Infiniflash is 512TB in a 3U chassis that is SAS-connected. You can front this with something like DataCore's SANsymphony to turn it into a NAS/SAN appliance.
The pricing looks to be around $1/GB, which is a ton cheaper than building a SAN of that capacity, plus it's much smaller in power/space/cooling.
Aah, managed to download this plugin and get it working. It connects to a different server than chat.facebook.com as well.
I've noticed in the comments that some folks can still use xmpp with chat.facebook.com, but whatever local server that DNS is pointing me at is no longer accepting connections.
Thanks.
Pretty much all of them as we move into 3D NAND... I know samsung has one out already as the 850 EVO... everyone should be right behind them with similar products.
Newer 3D NAND is using a charge trap design which basically solves the electron leakage issue found with the older floating gate NAND...
Also, the move to the newer 3D NAND brings us back up to 40nm processes vs the 10nm gates we are currently working with, allowing for much better reliability.
Disclaimer: I've been selling enterprise flash storage for the last 6 years.
I get hit with 1-2 job opportunities every day or two from LinkedIn alone...
Some are good, some are cruft... it all becomes noise since I'm not looking for a job right now.
You can't read game files faster because the process that reads the game file is single threaded vs multi-threaded... so it can only read as fast as a single thread can read.
A fully saturated CPU has enough lanes to do about 26-28GB/sec, but a single I/O thread might only be able to do 100-200MB/sec.
There was never any reason in the OS before today to make that any faster because the spinning disks that fed data to the CPUs couldn't do more than 100MB/sec.
Now that we have all this great flash, code needs to be re-written to be able to use other idle CPU time to spin up more threads and read the data faster.
It's worth remembering that 98k IOPS will be at a very small block size and will rapidly drop as you increase block size to 4K-1MB as the larger transfer size will directly equate to less I/O.
The real problem is that apps are not written for multi-threaded I/O which is what you really need in order to take advantage of the throughput provided by PCI-e flash.
Booting from RAID is more supported, and the support is baked into nearly every BIOS out there... booting PCI-e over NVMe or UEFI is brand new and very few things support it and all the code is new.
Booting through a raid card that has it's own BIOS is nothing like booting off of a native PCI-e device.
Booting from pci-e uses either a UEFI driver or NVMe today, two technologies that are kinda in their infancy.
The code is not yet fully optimized/etc and you may see reduced speeds at least until you can get into an OS layer and load up a more feature-full driver.
The PCI-e native SSDs are indeed faster, the problem is, the code reading data off of them (your application/os) isn't written to take advantage of the increased speeds. Single threaded reads cap out at the read speed of a single thread, and that isn't that fast. This is especially true if they are 4K reads vs 1M reads, as you aren't going to saturate anything until you get up into larger read sizes.
To really take advantage of the bandwidth SSDs enable, you need to be running multiple parallel apps running multiple reads, or you need an app that can do multi-threaded reads.
This is because you get stuck leaving the CPU to handle all the context switching between virtual block storage in DRAM and memory. The CPU has to copy data out of block and into memory before it can actually use it, so by making a ram disk you end up giving the CPU 2-4x the amount of work to do for what should be a DMA read/write, which would normally be offloaded.
Also, your reads from your game are going to be single-threaded, and a single read/write thread is going to be pretty slow.
That's how I do it at least...