Category Archives: Sh*ts

Data center fabric, the next-generation Facebook data center network and “How we scaled Instagram”, by Mike Krieger

Introducing data center fabric, the next-generation Facebook data center network

The more than 1.35 billion people who use Facebook on an ongoing basis rely on a seamless, “always on” site performance. On the back end, we have many advanced sub-systems and infrastructures in place that make such a real-time experience possible, and our scalable, high-performance network is one of them.

Facebook’s production network by itself is a large distributed system with specialized tiers and technologies for different tasks: edge, backbone, and data centers. In this post, we will focus on the latest developments in our data center networking and unveil the next-generation architecture that we have successfully deployed in our new Altoona facility: data center fabric.

https://code.facebook.com/posts/360346274145943/introducing-data-center-fabric-the-next-generation-facebook-data-center-network

“How we scaled Instagram”, by Mike Krieger (video)

Mike Krieger, co-founder of Instagram, talks about their tech setup, how they scaled from one server in LA, to AWS and ultimately Facebook’s own infrastructure.

https://opbeat.com/blog/posts/how-we-scaled-instagram-mike-krieger/

 

rackspot changed his name to easyhost

rackspot.pt changed his name to easyhost.pt … this is what happened…

they are now using online.net infrastructure… my blog, hosted on rackspot.pt – now on easyhost (online.net) is getting lot of database errors…. looks like they are even using the db connections limits…. fuck!

time to move!..
i already own a dedibox @ online.net … time to move it all.

UPDATE!! OK THEY WERE UNDER A DDOS ATTACK!
THATS WHY CONNECTIONS FAILED.

Raid 1 and Raid 0 explained

 

I’m afraid you dont even get something as simple as:
Raid 1 : faast
Raid 0 : slow

Raid 1 brings safety by allowing you to half of screwed drives
Raid 0 brings you the comfort to know that when a drive is crashed, you can go home. To cry.

But speed wise it’s a different story:
Raid1:
– You have twice the same data, so write speed should be, let’s say, “normal
– You have 2 disks to read from. With the proper disks, controllers and bla bla, you read faster.

Raid 0:
– You write faster
– You read faster

So, in some cases where you require those little boosts, and the data is not “i’m going to kill myself if i lose this” important, then why not, just stack a few extra drives nearby ;)

In jflory’s case, a failed drive, would mean both drives are not useable, then waiting for the replacement, and timing … Yes that’s a lot of downtime for gaining a few G you might be able to save up anyway.

Dont be that guy Jflory!


http://www.spigotmc.org/threads/raid-1-raid-0-soyoustart-myth-busting.11171/#post-127898

Who remembers ARJ?

ARJ has a 10-plus year track record of good speed, compression and the most flexibility of any archiver. In addition, it will run on most PCs from the IBM PC XT to Pentium IIIs and is compatible from version 1.0 to present.

The major features of ARJ 2.86 include:

  • Windows 95, 98, Millenium long filename support in ARJ
  • Windows style wildcard support
  • Ability to execute a command after self-extraction of files
  • Automatic handling of more than 99 volumes
  • Ability to process and archive up to 50,000 files at one time (registered support for up to 260,000 files at one time)
  • Ability to store up to 250 backups (chapters) within a single archive and restore any specific backup
  • Excellent file compression in terms of resulting archive size and speed
  • Unmatched flexibility in archiver usage
  • Support for Windows file date-time created and accessed
  • Data damage protection option storing data within the archive
  • Improved chapter archive and multiple volume support
  • Year 2000 compliance

 

 

Weird facebook.com whois!

 

$ whois facebook.com

Whois Server Version 2.0

Domain names in the .com and .net domains can now be registered
 with many different competing registrars. Go to http://www.internic.net
 for detailed information.

FACEBOOK.COM.DISABLE.YOUR.TIMELINE.NOW.WITH.THE.ORIGINAL.TIMELINE-REMOVE.NET
FACEBOOK.COM.GET.ONE.MILLION.DOLLARS.AT.WWW.UNIMUNDI.COM
FACEBOOK.COM.LOVED.BY.WWW.SHQIPHOST.COM
FACEBOOK.COM.MORE.INFO.AT.WWW.BEYONDWHOIS.COM
FACEBOOK.COM.ZZZZZ.GET.LAID.AT.WWW.SWINGINGCOMMUNITY.COM
FACEBOOK.COM

How to do a correct whois:  whois =facebook.com

 

WTF?

More readings about it
http://superuser.com/questions/30388/strange-whois-results
http://serverfault.com/questions/265750/twitter-coms-weird-whois-what-is-going-on

 

 

Preload images with JavaScript without frameworks

Here’s a good article about how to preload pics/images without frameworks.

There are two scenarios here. Case 1: you just want to load all your images prior to displaying the rest of your page. Whether that’s because you like it this way or you need to get the browser to ‘know’ your images widths and heights first, preload a gallery of images, it does not matter. The arguments for ‘speeding up’ page loads are a bit moot now, with modern connections and modern browsers there are no great benefits to this. Either way, you need to arrange your code in a way that allows you totrigger some event or function when the loading is complete in order to continue displaying your site.

And then, there’s case 2: pre-emptive image loading / cache priming, which is the more interesting use. This is a relatively new trend that involves examining the user’s browsing pattern and anticipating what they do next. For instance, if they are browsing product listings as a result of a search with 100 results (20 per page), it is almost safe to assume they may want to go to page 2 or 3. It is also safe to assume the average user would take a while to finish appraising their results, scroll down and locate the ‘next’ link. This idle slot is where you can put their connection to better use by priming the browser cache with the product thumbnails of the next results page. In this instance, you don’t really care for any onload / oncomplete events, the benefits of the cache will be reaped on the next page instead.

Read it all on http://fragged.org/preloading-images-using-javascript-the-right-way-and-without-frameworks_744.html