DomKen
Posts: 19457
Joined: 7/4/2004 From: Chicago, IL Status: offline
|
quote:
ORIGINAL: Phydeaux quote:
ORIGINAL: mnottertail quote:
Well, if you and Ken want to look into it, you will find that they have a different mechanism for error correction for large drive arrays. Don't let me stop you guys from going and educating yourself. As for indexing - again commercial indexes were doing 43 billion files in an hour. I don't know how that scales. Ken already explained RAID, but yeah, I am aware of the different error mechanisms having been a computer programmer that geeked in places the depth and breath of this country, for over twenty years and creating (not alone) the E911 system (among other things) for verizon, and oh, and voice compression and recognition for automated operators for verizon. And have done most of my work in telephony and computing gizmos. Yanno, like telemarketing stuff. Hooking telephones and computers together to transform that stuff. Yeah, cute shit on indexing, you ain't in the universe, let alone the galaxy.0 And I've been in the IT industry for longer than that. And I can tell you quite interesting stories about the e911 and the ESS switches as well as the 4.0 switches. And I've implimented literally hundred of raids systems. And again, I can tell you regardless of what FactlessKen thinks that Raid is not the methodology used for very large arrays. Doesn't meet the requirements for scaleable and time response, as well as the addressing requirements. And if you have the experience you claim with voice compression - you know that the data rate for a voice line is miniscule. Regarding indexing - no one ever said they are indexing by conversation content - nor are they. The indexes are #, date, time. With the voice recorded for analyst playback. Likewise for the internet by ip address. Additionally, google and others cache huge amounts of web page data. Once a cached image is tokenized it compression is huge. You don't have to analyze and store packet traffic. So what is this mysterious not RAID system for ensuring data integrity? No one I know of uses anything else and I've never even heard of a competitor. And how exactly could any system achieve the goal without mirroring the stored data on multiple separate drives? Any system that doesn't rely on mirroring surely involves data loss when a single drive fails. Yes, you would need to store the data at packet level. To do otherwise would require building up the packets received into the various requests and responses in real time. That would crush any super computer going. BTW, if you throw away the packet data what do you think you'd have? Trillions of web requests and responses with no idea who received them. As to compression you cannot use any kind of lossy compression due to steganography. Once you're dealing with lossless compression images and video do not compress usefully and the reason to do compression in the first place would be to store all of that (all the text sent over the net is probably a miniscule portion of the bandwidth).
|