Free wi-fi municipal networks are springing up in Brazil since at least 2009. Nonetheless, as these networks are intended for public access to government services, people still buy 30Mbit+ broadband connections for their homes from the big telcos.
Verizon's Accidental Mea Culpa Mark Taylor / 23 hours ago
David Young, Vice President, Verizon Regulatory Affairs recently published a blog post suggesting that Netflix themselves are responsible for the streaming slowdowns Netflix's customers have been seeing. But his attempt at deception has backfired. He has clearly admitted that Verizon is deliberately constraining capacity from network providers like Level 3 who were chosen by Netflix to deliver video content requested by Verizon's own paying broadband consumers.
His explanation for Netflix's on-screen congestion messages contains a nice little diagram. The diagram shows a lovely uncongested Verizon network, conveniently color-coded in green. It shows a network that has lots of unused capacity at the most busy time of the day. Think about that for a moment: Lots of unused capacity. So point number one is that Verizon has freely admitted that is has the ability to deliver lots of Netflix streams to broadband customers requesting them, at no extra cost. But, for some reason, Verizon has decided that it prefers not to deliver these streams, even though its subscribers have paid it to do so.
The diagram then shows this one little bar, suggestively color-coded in red so you know it's bad. And that is meant to be Level 3 and several other network operators. That bar actually represents a very large global network, and it should be shown in green, since, as we will discuss in a moment, our network has plenty of available capacity as well. In my last blog post , I gave details about how much fiber and how much equipment we deployed to build that network and how many cities around the globe it connects. If the Verizon diagram was to scale, our little red bar is probably bigger than their green network.
But here's the thing. The utilization of all of those thousands of links across the Level 3 network is much the same as Verizon's depiction of their own network. We engineer it that way. We have to maintain adequate headroom because that's what we sell to customers. They buy high quality uncongested bandwidth. And in fact, Verizon admits as much because they conveniently show one direction across our network with a peak utilization of 34%; almost exactly what I explained in my last blog post. I can confirm once again that all of those thousands of links on the Level 3 network are managed carefully so that the peak utilizations look very similar to those Verizon show for their own network â" IN BOTH DIRECTIONS.
So why does Verizon show this red bar? And why do they blame Level 3 and the other network operators contracted by Netflix?
Well, as I explained in my last blog post, the bit that is congested is the place where the Level 3 and Verizon networks interconnect. Level 3's network interconnects with Verizon's in ten cities; three in Europe and seven in the United States. The aggregate utilization of those interconnections in Europe on July 8, 2014 was 18% (a region where Verizon does NOT sell broadband to its customers). The utilization of those interconnections in the United States (where Verizon sells broadband to its customers and sees Level 3 and online video providers such as Netflix as competitors to its own CDN and pay TV businesses) was about 100%. And to be more specific, as Mr. Young pointed out, that was 100% utilization in the direction of flow from the Level 3 network to the Verizon network.
So let's look at what that means in one of those locations. The one Verizon picked in its diagram: Los Angeles. All of the Verizon FiOS customers in Southern California likely get some of their content through this interconnection location. It is in a single building. And boils down to a router Level 3 owns, a router Verizon owns and four 10Gbps Ethernet ports on each router. A small cable runs between each of those ports to connect them together. This diagram is far simpler than the Verizon diagram and shows exactly where the congestion exists.
I converted my Delphi app from firebird to postgresql because of scalability problems. Serious scalability problems. Firebird is good, but not nearly as grate as PostgreSQL (as a database engine). It simply cannot work with tables holding a few million records (the server crawls). An almost direct conversion to PostgreSQL gave the app the speed it needed (and afterlife to the server).
> One of the big ones for me currently is that the query > optimizer only uses one index in queries. I know you can have > multi-column indexes, but I still see this being a problem for > some of my more complex queries. Does PostgreSQL do this > better? Informed opinions please, rather than fanboy noise.
PostgreSQL joins indexes as necessary, like Interbase/Firebird. PG scales just fine too. The company I work for uses PostgreSQL as main DB server (migrated from Interbase and MS SQL before that). It's the best database server we've used so far. We did not conseder MySQL because of the lack of transactions, triggers and SP's.
I know, this is problably not what you are looking for, it's just the informed opinion of a regular, satisfied PG user.
Slashdot Mirror
Free wi-fi municipal networks are springing up in Brazil since at least 2009. Nonetheless, as these networks are intended for public access to government services, people still buy 30Mbit+ broadband connections for their homes from the big telcos.
Here is a copy of the text, just in case:
Verizon's Accidental Mea Culpa
Mark Taylor / 23 hours ago
David Young, Vice President, Verizon Regulatory Affairs recently published a blog post suggesting that Netflix themselves are responsible for the streaming slowdowns Netflix's customers have been seeing. But his attempt at deception has backfired. He has clearly admitted that Verizon is deliberately constraining capacity from network providers like Level 3 who were chosen by Netflix to deliver video content requested by Verizon's own paying broadband consumers.
His explanation for Netflix's on-screen congestion messages contains a nice little diagram. The diagram shows a lovely uncongested Verizon network, conveniently color-coded in green. It shows a network that has lots of unused capacity at the most busy time of the day. Think about that for a moment: Lots of unused capacity. So point number one is that Verizon has freely admitted that is has the ability to deliver lots of Netflix streams to broadband customers requesting them, at no extra cost. But, for some reason, Verizon has decided that it prefers not to deliver these streams, even though its subscribers have paid it to do so.
The diagram then shows this one little bar, suggestively color-coded in red so you know it's bad. And that is meant to be Level 3 and several other network operators. That bar actually represents a very large global network, and it should be shown in green, since, as we will discuss in a moment, our network has plenty of available capacity as well. In my last blog post , I gave details about how much fiber and how much equipment we deployed to build that network and how many cities around the globe it connects. If the Verizon diagram was to scale, our little red bar is probably bigger than their green network.
But here's the thing. The utilization of all of those thousands of links across the Level 3 network is much the same as Verizon's depiction of their own network. We engineer it that way. We have to maintain adequate headroom because that's what we sell to customers. They buy high quality uncongested bandwidth. And in fact, Verizon admits as much because they conveniently show one direction across our network with a peak utilization of 34%; almost exactly what I explained in my last blog post. I can confirm once again that all of those thousands of links on the Level 3 network are managed carefully so that the peak utilizations look very similar to those Verizon show for their own network â" IN BOTH DIRECTIONS.
So why does Verizon show this red bar? And why do they blame Level 3 and the other network operators contracted by Netflix?
Well, as I explained in my last blog post, the bit that is congested is the place where the Level 3 and Verizon networks interconnect. Level 3's network interconnects with Verizon's in ten cities; three in Europe and seven in the United States. The aggregate utilization of those interconnections in Europe on July 8, 2014 was 18% (a region where Verizon does NOT sell broadband to its customers). The utilization of those interconnections in the United States (where Verizon sells broadband to its customers and sees Level 3 and online video providers such as Netflix as competitors to its own CDN and pay TV businesses) was about 100%. And to be more specific, as Mr. Young pointed out, that was 100% utilization in the direction of flow from the Level 3 network to the Verizon network.
So let's look at what that means in one of those locations. The one Verizon picked in its diagram: Los Angeles. All of the Verizon FiOS customers in Southern California likely get some of their content through this interconnection location. It is in a single building. And boils down to a router Level 3 owns, a router Verizon owns and four 10Gbps Ethernet ports on each router. A small cable runs between each of those ports to connect them together. This diagram is far simpler than the Verizon diagram and shows exactly where the congestion exists.
lvltvzw
Verizon has
Two kinetic sensors (back and front). That would be nice...
Plus, TS, CIFS and binary compatibility capabilities.
Biologically, in this case, the chance is always 50%-50%!
All your smartphones are belong to us.
Bad RAM, apparently...
Dont't you read Slashdot? http://mobile.slashdot.org/article.pl?sid=08/08/27/1334214
That's what Make3D does... http://make3d.stanford.edu/
But friends call it "Murphy".
Would the Sun face the same side of the planet? Eternal day/night?
1. Dont certify current software version;
2. Release new certified major version, users WILL upgrade...;
3. ???
4. Profit.
Apparently it means "Revolution"...
(you seid you did not care!!)
http://www.gsmarena.com/sony_ericsson_k800-1485.ph p
Oh, oane more thing: server load was always 99.9% full. Now with PostgreSQL it's always 0.1%. :)
What are your server specs? The server was a dual pentium 3 at 933 MHz with 1Gb RAM. The database was 4Gb+ in size.
We did not expect this kind o problem... we are prety sure about what we do in Delphi/SQL.
Are they made for Pen-Test, Forensics & Recovery?
I converted my Delphi app from firebird to postgresql because of scalability problems. Serious scalability problems. Firebird is good, but not nearly as grate as PostgreSQL (as a database engine). It simply cannot work with tables holding a few million records (the server crawls). An almost direct conversion to PostgreSQL gave the app the speed it needed (and afterlife to the server).
PostgreSQL has it all...
/ d ex.html
Windows port: http://www.postgresql.org/ftp/binary/v8.1.3/win32
GUI Tool: http://pgadmin.org/ (comes with the windows install)
Lots of documentation: http://www.postgresql.org/docs/8.1/interactive/in
Books: http://www.postgresql.org/docs/books/
And don't repeat my mistakes, you should always mind scalability.
http://www.opamerica.com/product_info.php/products _id/781
Firebird lacks the scalability of PostgreSQL.
FIX IT!!!!!!
> One of the big ones for me currently is that the query
> optimizer only uses one index in queries. I know you can have
> multi-column indexes, but I still see this being a problem for
> some of my more complex queries. Does PostgreSQL do this
> better? Informed opinions please, rather than fanboy noise.
PostgreSQL joins indexes as necessary, like Interbase/Firebird. PG scales just fine too.
The company I work for uses PostgreSQL as main DB server (migrated from Interbase and MS SQL before that). It's the best database server we've used so far. We did not conseder MySQL because of the lack of transactions, triggers and SP's.
I know, this is problably not what you are looking for, it's just the informed opinion of a regular, satisfied PG user.
(sorry my English)
RTFA!
I almost forgot that this is Slashdot and you must RTFA before you read the comments or you get angry because of the distorted headlines.
That would be Gnome XP or KDE XP or whatever-window-manager-you-are-running-XP. The kernel would be Linux NT. \m/