barsxl

5 ms·

1.
by barsxl 3y ago
Automattic | Remote | Full-time | Senior Systems Engineer (Systems Wrangler) | $110-$210k+ We're looking for the world's best systems engineers to help build and maintain the infrastructure that supports over a billion people each
2.
by barsxl 3y ago
Automattic | Remote | Full-time | Senior Systems Engineer (Systems Wrangler) We're looking for the world's best systems engineers to help build and maintain the infrastructure that supports over a billion people each month across
3.
by barsxl 3y ago
Automattic | Remote | Full-time | Senior Systems Engineer (Systems Wrangler) We're looking for the world's best systems engineers to help build and maintain the infrastructure that powers tens of billions of page views and support
4.
by barsxl 3y ago
Thanks for the heads up. We have removed this file from the platform for now while we review.
5.
by barsxl 4y ago
Thanks for pointing that out. I fixed the post.
6.
by barsxl 10y ago
> Can you elaborate just a smidge? Is WordPress.com, for example, not encrypting content when it's requested by iTunes? (Thanks!) Yes, we have some targeted exceptions for incompatible clients.
7.
by barsxl 10y ago
Many of the larger webhosts have free (but not mandatory) SSL support in production, beta, or on their near-term roadmap.
8.
by barsxl 10y ago
This happens with the https:// vary rarely. The http:// case happens more often. This is one of the complications in adding HSTS headers with includeSubDomains. Right now, the http:// version works as
9.
by barsxl 10y ago
Photon[0] does exactly this (and more!) and is free to use as part of Jetpack[1] 0. http://developer.wordpress.com/docs/photon/ 1. https://wordpress.org/plugins/jetpack/
10.
by barsxl 10y ago
Yes, we're working on it.
11.
by barsxl 10y ago
> I believe it's breaking podcast feeds being served with WordPress.com, because iTunes doesn't support Let's Encrypt certificates. Do you have an example? We have already implemented workarounds for iTunes. If they aren
12.
by barsxl 13y ago
WordPress.com offers two-step authentication for all of our users. You can use any application which supports Time-Based One-Time Passwords (TOTP) such as Google Authenticator, Authy, etc. and you can also receive a one time password via
13.
by barsxl 13y ago
WordPress.com has pretty sophisticated brute force detection mechanisms and protections in place. I am not sure why you would say otherwise.
14.
by barsxl 14y ago
The majority of our transient bugs on WordPress.com are probably related to APC opcode issues. We try to catch them and handle it gracefully, but it isn't always so easy.
15.
by barsxl 14y ago
Of the 2000 servers, about 90% of them are running something related to WordPress.com. There are 36 "load balancer" servers in total. I added up the req/sec across those 36 machines and came up with the 70k/sec number in the article. The
16.
by barsxl 14y ago
WordPress.com currently has 12 load balancers per data center. They are HA and used for different subsets of traffic.
17.
by barsxl 14y ago
We started using Percona's MySQL builds by default a couple of years ago. There are some nice performance and convenience features not included in the MySQL.com builds. (Un)fortunately we still have quite a few MySQL 4.1 instances happily
18.
by barsxl 14y ago
Many more dynamic pages than you would expect. We do hundreds of thousands of database queries/sec. We do some caching with Batcache - http://wordpress.org/extend/plugins/batcache/ but it's more to handle large spikes in traffic for sin
19.
by barsxl 14y ago
As with any tiered web application, the requests aren't evenly distributed across all the servers :) Most of our main Nginx proxies serve about 5k req/sec and have about 50k established connections. They are usually 8 cores + HT for a tot
20.
by barsxl 14y ago
WordPress.com hasn't run on FreeBSD since the TextDrive days which was way before Layered Tech, before me and before WordPress.com was open to the public. We are 100% Debian today, but have used Ubuntu in the past. We never really used HA
21.
by barsxl 14y ago
We serve about 150k req/sec from the CDN. That (obviously) isn't included in the 70k number from the article. The 70k is only what we are serving from the origin.