Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror

Comment Re:why is the system not master / master or slave (Score 3, Interesting) 82

there is physical distance between main and backup site. that means there are physical limitations how fast transaction can be done if you require master/master configuration (you are limited by speed of signal propagation). to ensure both sides to have same data (sync replication) you need 2x time distance. that means high latency. and stock exchange wants to have low latency as much as possible. so only design is to have main / DR (DR being async copy).

Comment tech advances (Score 1) 57

Accept that your puny 5 senses will be perfectly simulated ... soon. then Reality goes by by .. tech evolution is going forward, and humans are mostly standing in one place. many years ago audio recording was "proof" and is then faked, then still image was "proof" and Photoshop enabled to make any you want, now artificial video is created good enough and no longer "proof". we just need simulated smell, taste and touch and we are done :)

Comment dislike after looking casually at draft (Score 1) 258

from Draft: The IP addresses and ports can change in the middle of a connection. ad/js/css blocking will be much more difficult, as browser probably dont have proper API for plugins to kill those. blocking will probably need to move to some proxy (which need to be done from scratch) also browser should be put in separate linux namespace to avoid ability to go-around proxy. iptables support for this protocol woud be much more complicated as there is now mixing of data/tranasport/security features ... IMHO .. garbage (just to gain few ms in latency)

Comment Re:Signs clear enough even for a layman (Score 1) 581

first on my mind list:

- parallel read/write to multiple disk in RAID5 in btrfs (speed!, specially when multiple reading/writing userspace processes on btrfs which contains 10+ disks)

- pull back multi-path mgmt at FibreChannel driver level in kernel (WTF userspace need to know that scsi device have multiple path, userspace just get device and use it, rest is kernel work to handle, IMHO)

- throw out interface teaming (bonding is more that good, long time used in production, with VLAN tagging. 0 problems :)

p.s. you ask for Linux, not GNU Linux. Right? :)

Slashdot Top Deals

Hold on to the root.

Working...