1

00:00:01,310 --> 00:00:07,280

So I've given you a bunch of reasons why I think that building a Web application engo is a really good



2

00:00:07,280 --> 00:00:07,800

idea.



3

00:00:07,820 --> 00:00:13,430

And let me give you an example to show you just how much more efficient something written and go is



4

00:00:13,430 --> 00:00:14,450

than something written in.



5

00:00:15,680 --> 00:00:17,480

So right now I'm looking at lineout.



6

00:00:17,480 --> 00:00:21,290

And Lynard is a service that allows you to have virtual private servers.



7

00:00:21,290 --> 00:00:23,830

So Digital Ocean has the same thing.



8

00:00:23,840 --> 00:00:24,710

They're called droplets.



9

00:00:24,710 --> 00:00:28,180

Later in this course will be deploying a A server.



10

00:00:28,190 --> 00:00:29,060

I'm going to use Lynard.



11

00:00:29,060 --> 00:00:31,340

You can use whatever you want if you choose to deploy one.



12

00:00:32,090 --> 00:00:34,760

But I have two servers I want to show you.



13

00:00:34,760 --> 00:00:36,140

One is called Ghost Server.



14

00:00:36,140 --> 00:00:37,070

And let's look at that.



15

00:00:37,910 --> 00:00:38,810

That's in Toronto.



16

00:00:38,900 --> 00:00:40,640

It has four CPU cores.



17

00:00:40,640 --> 00:00:43,640

It has eight gigs of RAM and 160 gigs of storage.



18

00:00:43,640 --> 00:00:44,750

So that's go server.



19

00:00:45,170 --> 00:00:46,940

And the other one is called Romulus.



20

00:00:47,450 --> 00:00:53,780

And Romulus also has four CPU cores, also has eight gigs of RAM and also has 160 gigs of storage.



21

00:00:54,260 --> 00:01:00,680

And I'm going to go over to my I'll just hide this and go over to here.



22

00:01:01,190 --> 00:01:02,390

Let me get there eventually.



23

00:01:02,990 --> 00:01:07,430

OK, let me bring up my terminals so I have two windows open.



24

00:01:07,520 --> 00:01:08,930

One is connected to go server.



25

00:01:08,960 --> 00:01:11,960

This is a server that is running some go applications.



26

00:01:12,320 --> 00:01:20,690

And if I go to VA, W-W and else, other sites and else you'll see I have this many applications.



27

00:01:20,690 --> 00:01:25,760

These are all go applications, every single one of them, except for Disk and Tusi data.



28

00:01:25,760 --> 00:01:28,280

Everything else is an application written and go.



29

00:01:28,280 --> 00:01:29,570

And they are there are a lot.



30

00:01:29,570 --> 00:01:37,820

There's what one, two, three, four, five, six, seven plus eight is fifteen plus seven is 22 applications



31

00:01:37,820 --> 00:01:42,530

all written and go all running on this server, this one Romulus.



32

00:01:42,530 --> 00:01:45,950

Let's go to our Web sites and else.



33

00:01:46,100 --> 00:01:50,420

It has about the same number of applications and every one of these is written in.



34

00:01:51,680 --> 00:01:55,250

The majority of them are there might be one static site there, but the majority of them are actually



35

00:01:55,250 --> 00:01:57,530

written using Laravel in P.



36

00:01:58,640 --> 00:02:04,280

So I'm going to now run an application called Top on this server and I'll run the same application called



37

00:02:04,280 --> 00:02:05,450

Top on this server.



38

00:02:05,450 --> 00:02:08,030

Remember, the one on the left is running go applications.



39

00:02:08,450 --> 00:02:15,110

Look at its load, average point zero four and look at the load average on this one point eight nine.



40

00:02:15,470 --> 00:02:21,620

So it's using far more resources to run about the same number of websites, which all have about the



41

00:02:21,620 --> 00:02:27,740

same amount of traffic, a fair bit of traffic, but it's far more efficient to run something and go



42

00:02:27,740 --> 00:02:28,880

than it is to run something in.



43

00:02:29,690 --> 00:02:31,760

And look at the memory usage again.



44

00:02:31,760 --> 00:02:39,500

You know, we have much less memory being used in go than there is over here on on P.



45

00:02:39,980 --> 00:02:46,910

And if you look at the uptime, this server has been running for 11 days and the uptime for the server,



46

00:02:47,060 --> 00:02:48,530

it's been running for 17 days.



47

00:02:48,530 --> 00:02:50,870

So they've been running for about the same amount of time.



48

00:02:51,140 --> 00:02:59,540

And yet the load usage, the amount of system resources consumed by Laravel is vastly higher than it



49

00:02:59,540 --> 00:03:06,380

is in go, so that if nothing else is a compelling reason to use a comp. language rather than an interpreted



50

00:03:06,380 --> 00:03:06,950

language.