Uh, he took hostages and threatened to use a bomb, the obvious solution is a bullet through the brainstem. I'm fairly anti-cop myself as I think they need to be put back in their place as public servants who are more beholden to the law than your average citizen due to the extraordinary privileges and responsibilities given to their position, but even I can see that this is the correct course of action. If you threaten mass harm to people you need to be eliminated from the picture before you can carry out your threats. This is one of the few things the police force should actually be used for.
Because when you are applying the patch you shouldn't be going through a transaction rollback! Applying a patch should involve the graceful shutdown of the database.
And the population in India is growing MUCH faster so that India will actually overtake China for most populous nation after not too long. The Chinese one child policy (though often worked around) has had a definite effect in curbing their population growth.
Really? Then my load must be very a-typical because I have about a rackfull of database servers and another rack of 144GB x5570 VM servers hitting a half full 6400 and it's not complaining let alone being ground to dust =) Now I'm not doing VDI because I haven't seen a TCO calculation that passes the smell test but from what I've seen in benchmarks and white papers putting a few of the HP SSD's into the 6400 should settle the boot storm problem. Is it possible to completely overwhelm such a SAN with just a few nodes, sure but those aren't typical workloads for ~99% of the customer base.
Oh, that VMS stuff had been patched, and the hardware failures were taken care of too, I doubt any single cluster node had an uptime of more than 5-8 year =) It's precisely because they were designed around online patching, node failover, etc that such a feat could be accomplished. Of course the patching probably wasn't as time critical as a modern system that has to deal with the entire world of zero day exploits so things were probably much more rigorously tested then they can be today.
TMS already made such a product with their RAMSAN, it's a niche player for those who need more IOPS than god and don't need to store very much (ie a niche market). Their top end product claims to do 5M IOPS, 60GB/s sustained but only stores 100TB which is the size of a midend array like a loaded HP EVA 6400 but costing about 20x more (granted the EVA tops out in the tens of thousands of IOPS, but that's enough for the vast majority of workloads).
Eh, hope that server isn't going to be doing anything transactional, the only Intel SSD I'd trust in any of my servers that actually need SSD's is the X-25e which I have actually used.
Some supercapacitors have made it to market and refinements on lithium technologies have come a long way in the last decade, tripling the maximum storage density available. The problem is our demand for portable power has outstripped that growth (my blackberry is significantly more powerful than my desktop from 10 years ago and talks 6 different wireless protocols).
Hardware failure and hardware upgrade can be handled by VMWare FT assuming your app fits into 1 vCPU (this will probably be relaxed in the future but I have heard nothing about even experimental support for vSMP yet).
Recovering a high transaction load system from an ungraceful shutdown is completely different from a clean shutdown and reboot. Saying that transaction rollback is the same as boot time is disingenuous.
Any open system that takes over 10 minutes to boot is seriously broken. Even my 16 core 256GB machines with multiple HBA's takes under 5 minutes to reboot, yes they run Oracle (Enterprise but not RAC). They even have almost two dozen LUN's mapped.
China has labor but they have a slight problem in that they killed off two generations of their smartest people and decimated any semblance of independent thinking in their academic institutions. They will recover from this but if you think they will overcome it in a decade or two you are delusional.
Try heating a nanowire with a high enough voltage, it will get pretty damn hot, now have that in contact with a couple atoms thick layer of crude and you now have combusted crude. These kids are from MIT, they are most likely MUCH smarter than you, if they say their prototype works, it probably does =)
No, that's 2m^2 so ~10KWhrs or solar insolation at 0 degrees tilt in the gulf of mexico on average, take an "average" solar panel at 15% efficiency and you get 1.5KWhrs devide by 24 hours and you get 62.5W so they must be assuming ~24% efficient cells which are fairly expensive. An interesting approach would be to use microbes to break the crud into gasses and feed the gasses into fuel cell, more efficient but probably not as fast =)
Rare earth metals, the easily mined deposits of which our civilization will probably have depleted in the next 50-100 years. Already there are serious concerns about switching to renewable energy sources based on the low availability of certain key resources.
You could actually do symbolic links in 2000, they were just very hacky and not supported by all OS methods. It's because NTFS had reparse points that this worked.
HR's the only one with the buzzword matching filter, and lord help any IT department that lets HR do the actual hiring! We match for two things, technical skill and your ability to jell with the team, specific technologies are rarely that important (no must have 5 years experience with Windows 2008 here) because we figure any potential candidate who got that far and passes the sniff test can probably learn on the job.
*deduplication, correct
*symbolic links to files, incorrect NTFS has supported reparse points since Windows 2000
*no support for RAIDs, incorrect Server versions support RAID 0, 1, and 5
*no support for dynamic resizing, incorrect Windows 2003 added support for dynamic growth for non-system/non-boot volumes, 2008 added dynamic grow and shrink for all volumes.
It also supports compression, encryption, ACL's, Metadata, and ridiculously large volumes and files.
I'm very impressed with NTFS, the last time I lost data on an NTFS volume that wasn't caused by a hardware fault was back in the NT4 days. It handles non graceful shutdowns better than just about any other FS I've worked with.
Slashdot Mirror
Uh, he took hostages and threatened to use a bomb, the obvious solution is a bullet through the brainstem. I'm fairly anti-cop myself as I think they need to be put back in their place as public servants who are more beholden to the law than your average citizen due to the extraordinary privileges and responsibilities given to their position, but even I can see that this is the correct course of action. If you threaten mass harm to people you need to be eliminated from the picture before you can carry out your threats. This is one of the few things the police force should actually be used for.
I printed my boarding pass from my blackberry to the internet printer at a hotel last month without any PC involved, quite convenient.
Because when you are applying the patch you shouldn't be going through a transaction rollback! Applying a patch should involve the graceful shutdown of the database.
And the population in India is growing MUCH faster so that India will actually overtake China for most populous nation after not too long. The Chinese one child policy (though often worked around) has had a definite effect in curbing their population growth.
490GB should be enough for as many linked clone's as you're likely to need.
Really? Then my load must be very a-typical because I have about a rackfull of database servers and another rack of 144GB x5570 VM servers hitting a half full 6400 and it's not complaining let alone being ground to dust =) Now I'm not doing VDI because I haven't seen a TCO calculation that passes the smell test but from what I've seen in benchmarks and white papers putting a few of the HP SSD's into the 6400 should settle the boot storm problem. Is it possible to completely overwhelm such a SAN with just a few nodes, sure but those aren't typical workloads for ~99% of the customer base.
Oh, that VMS stuff had been patched, and the hardware failures were taken care of too, I doubt any single cluster node had an uptime of more than 5-8 year =) It's precisely because they were designed around online patching, node failover, etc that such a feat could be accomplished. Of course the patching probably wasn't as time critical as a modern system that has to deal with the entire world of zero day exploits so things were probably much more rigorously tested then they can be today.
TMS already made such a product with their RAMSAN, it's a niche player for those who need more IOPS than god and don't need to store very much (ie a niche market). Their top end product claims to do 5M IOPS, 60GB/s sustained but only stores 100TB which is the size of a midend array like a loaded HP EVA 6400 but costing about 20x more (granted the EVA tops out in the tens of thousands of IOPS, but that's enough for the vast majority of workloads).
Eh, hope that server isn't going to be doing anything transactional, the only Intel SSD I'd trust in any of my servers that actually need SSD's is the X-25e which I have actually used.
Some supercapacitors have made it to market and refinements on lithium technologies have come a long way in the last decade, tripling the maximum storage density available. The problem is our demand for portable power has outstripped that growth (my blackberry is significantly more powerful than my desktop from 10 years ago and talks 6 different wireless protocols).
Hardware failure and hardware upgrade can be handled by VMWare FT assuming your app fits into 1 vCPU (this will probably be relaxed in the future but I have heard nothing about even experimental support for vSMP yet).
Or you're running VMS. The Irish national railway had a cluster uptime of 17 years back in 2007 when VMS turned 30 =)
Recovering a high transaction load system from an ungraceful shutdown is completely different from a clean shutdown and reboot. Saying that transaction rollback is the same as boot time is disingenuous.
Any open system that takes over 10 minutes to boot is seriously broken. Even my 16 core 256GB machines with multiple HBA's takes under 5 minutes to reboot, yes they run Oracle (Enterprise but not RAC). They even have almost two dozen LUN's mapped.
China has labor but they have a slight problem in that they killed off two generations of their smartest people and decimated any semblance of independent thinking in their academic institutions. They will recover from this but if you think they will overcome it in a decade or two you are delusional.
Try heating a nanowire with a high enough voltage, it will get pretty damn hot, now have that in contact with a couple atoms thick layer of crude and you now have combusted crude. These kids are from MIT, they are most likely MUCH smarter than you, if they say their prototype works, it probably does =)
No, that's 2m^2 so ~10KWhrs or solar insolation at 0 degrees tilt in the gulf of mexico on average, take an "average" solar panel at 15% efficiency and you get 1.5KWhrs devide by 24 hours and you get 62.5W so they must be assuming ~24% efficient cells which are fairly expensive. An interesting approach would be to use microbes to break the crud into gasses and feed the gasses into fuel cell, more efficient but probably not as fast =)
Rare earth metals, the easily mined deposits of which our civilization will probably have depleted in the next 50-100 years. Already there are serious concerns about switching to renewable energy sources based on the low availability of certain key resources.
You could actually do symbolic links in 2000, they were just very hacky and not supported by all OS methods. It's because NTFS had reparse points that this worked.
Yes, I've seen places where HR is given a requirements list and does the actual hiring from there on out.
The TI-89 is essentially embedded Maple.
HR's the only one with the buzzword matching filter, and lord help any IT department that lets HR do the actual hiring! We match for two things, technical skill and your ability to jell with the team, specific technologies are rarely that important (no must have 5 years experience with Windows 2008 here) because we figure any potential candidate who got that far and passes the sniff test can probably learn on the job.
*deduplication, correct
*symbolic links to files, incorrect NTFS has supported reparse points since Windows 2000
*no support for RAIDs, incorrect Server versions support RAID 0, 1, and 5
*no support for dynamic resizing, incorrect Windows 2003 added support for dynamic growth for non-system/non-boot volumes, 2008 added dynamic grow and shrink for all volumes.
It also supports compression, encryption, ACL's, Metadata, and ridiculously large volumes and files.
I'm very impressed with NTFS, the last time I lost data on an NTFS volume that wasn't caused by a hardware fault was back in the NT4 days. It handles non graceful shutdowns better than just about any other FS I've worked with.
There's also hardware VSS providers which are free to do things as they please wrt how they achieve the snapshot.