NightlyDev

I find it fun to thinker with high performance and high scalability designs, but I, as most others, have no need for it.

Start out small, make efficient systems and have scalability in the back of your head when doing so. Don't do as so many others: "Oh, this lib seems popular, let's just use that! Heck, the cart sometimes takes 8 minutes to load, we need to add more nodes on AWS!"

Yeah, stuff like that happens.

At least in my book optimization usually beats scalability as the place to start for more performance.

And 1K rps/core isn't something that's necessarily hard to achieve, if someone thinks otherwise.

I'm seeing about twice that on higly dynamic PHP pages with ~10 read/writes from/to MariaDB(running on the same machine).

How the hell can these pages have common load times of ~500ms? This must be the worst case pages, right? Hundreds of milliseconds is very slow if network latency is out of the picture.

It's definetly not always going to be a problem, but sometimes it does. ORM is always slower than writing custom code, but it might be more than fast enough.

One could do the same thing with other stuff too. Everything from bare metal to other application containers, and everything in between.

I do think that docker is very overhyped, but it does also solve some problems in a good way, even though it also creates new problems.

About firewalls and docker... It's so fu##ing annoying that docker changes the default iptables setting for forwarding when installed. :@

Send it in to get it fixed? How does that work? Do you get another laptop while you're waiting?

I'm used to Dell, and they replace hardware the next business day on location, even when I'm out traveling.

Not completely true. Apple sucks, and as a result of that iOS development is clearly more convenient on Mac OS.

I would also clearly prefer windows for projects supposed to run on windows servers, and Linux for projects supposed to run on Linux. Mac OS Server is utter crap and completely useless, so Apple doesn't have that going for it.

That's a myth. Fiberoptic cables are actually really robust.

That should definetly be fixed, but it's not something people will ever experience unless they try to write broken code by using undocumented features/sideeffects.

What exactly is it you know about the language that makes you hesitant to use it?

I'm not surprised.

You know that feeling when someone makes a service you really enjoy and you know you can trust? GitLab is definetly one of those services.

Self hosted? Check! Open source? Check! Community Edition that include the features small-medium teams need? Check!

I'm a huge fan of GitLab, and with the current business model and how community editions work I'll definetly continue promoting GitLab every chance I get.

Keep up the good work! :)

Well, there's nothing wrong with using PHP, and the performance is often better than with other comparable options. Personally I really enjoy PHP 7.

If you're way out of the loop then all you need to know is that PHP 7 is quite awesome.

Three second setup of PHP sites with atomic updates and automatic DB migrations:

Pre-built LXD image with MariaDB, nginx and PHP. Git for deployment.

Provisioned and live in three seconds with support for rollbacks, migrations, atomic updates and zero downtime.

Should work well for most other scripting languages too.

Actually very few services uses this kind of load balancing without relying on another service that does it for them.

If you're going to find patterns to decide what to block then you first need to make sure you receive all the traffic. If a single entry point can't handle it, well, then you need to load balance the incoming traffic.

How hard can it be to understand that businesses doesn't just hand out money without expecting anything in return? This is just stupidity and carelessness...

And clearly refinancing would be a good option to get a way better interest.

The easy answer: Load balancing

Anycast is the most important piece of the puzzle, allowing you to route traffic to a bunch of different locations.

Let's say you can handle 10 Gbps at a single location. If the traffic is evenly split between 100 destinations then you can have a single IP that can handle 1 Tbps of traffic.

Of course, the setup behind these IPs might vary a lot, and one might even use DNS load balancing in front of the IPs.

Just wait a couple of weeks until GDPR takes effect

Reading a bunch of small files from a volume is insanely slow from me in windows, so yeah...

Nodejs out of the box would ofc. be faster than PHP on something nodejs is born to do. But lets say we needed to do a bit of CPU work on each of these requests, then nodejs might struggle compared to PHP.

Both should be able to scale well in a "create a website and return the HTML"-scenario, and it's not unlikely that a PHP setup would be faster.

In a single page app thats mostly based on fetching data from an API nodejs would probably be faster.

About APCu: It's damn fast and very unlikely to slow you down, other stuff will probably bottleneck you way before APCu becomes a problem.

Use PHP as PHP, and nodejs as nodejs.

If you really need async in PHP or want to use PHP somewhat like nodejs then you should probably go for an extension and serve requests directly from PHP. I've had great experiences with that, serving over 500K simple HTTP req/s on a low end server.

But again, if max performance on a single server is so important then you should probably go for a compiled language anyways.

The person writing this has no idea about what he's talking about, so you're not the only one finding it untrustworthy.

Seriously, how can a person call himself a "PHP guru" and at the same time tell people that it's faster as a result of JIT compilation when PHP doesn't use JIT compilation? Amazing.

"JIT was integrated into PHP 7, which is why it has almost the same results as HHVM."

"PHP guru"

PHP doesn't use JIT compilation...

What do you mean by "scales to a reasonable degree"? How does others take over?

Tbh, a developer should be able to do the same thing if PSRs are used for the project.

You don't have to do everything yourself, most things are abstracted and easily accessible.

It's a framework, it's job is to make it easy to structure the site and handle common tasks for you. Laravel does have validation built in. You might have to put custom rules to use every now or then, but I don't see a way around that.

But laravel sure has its cost when it comes to performance - it's not possible to have it both ways.

Though it's not like you don't need experience with those same packages if you go the laravel way.

A developer shouldn't have an issue working with either. It's all PHP and all sane PHP frameworks are mostly based on the same concepts, with some tradeoffs here and there...

It's not that requires are hard to follow, it's just that you most likely don't want to mess around with requiring files manually instead of easily doing it by using autoloaders.

You can do it, but it's most likely a bad idea to mess around with it considering namespaces and such.

That page was actually shit. The font is really small and the text to background contrast is really bad on mobile.

I'm ashamed to be calling myself a web developer... What's up with everyone including tons of code from others, code they don't even know.

"Wooah, we need to toggle a class here!" "We got jQuery for that!"

"We also need to.." "Oh, we got this for that!"

Take this page as an example. It freaking huge, and the writer seems to think he has done a good job optimizing it now.

The page is really simple, and still a 1.66 MB JS bundle is required to even begin rendering the page.

And still the page doesn't work properly if you just do something as simple as view one external link and press the back button in an attempt to get back.

I know of a JS framework that might fix it, and it's only 7.6 MB. /s

Seriously, people should write about stuff they know.

Using the cloud is a waste of money as long as you don't need to scale up and down, or change the infrastructure frequently.

Bandwidth has always been insanely(!!) overpriced with most cloud providers.

I really enjoy GitLab and I've used it for five years now. I really like what GitLab is doing with the community version: free with all the features that makes sense for small to medium sized companies, or just a group of people.

Thank you for an awesome product! :)