Project

General

Profile

reduce server load and running as mywebsite/wtapplication

Added by Mohammed Rashad over 14 years ago

How to make server load minimum and optimize code to run faster wt application?

Is there any tool or anything which I can do code optimization for wt.

How to make my Wt application run faster on slow internet connections?

How to automatically restart a Wt application running on Wt built-in http server after a seg fault is occured.

I want to run my application on top of wthttp application but it should be available under the link

http:localhost/wt not as http://localhost:1001/

Is there any way to do that and auto restart after a seg fault.

Does running Wt as built-in http will increase the performance than running as wtfastcgi?


Replies (1)

RE: reduce server load and running as mywebsite/wtapplication - Added by Koen Deforche over 14 years ago

Mohammed Rashad wrote:

How to make server load minimum and optimize code to run faster wt application?

In general, you should avoid rendering widgets which are not visible.

Is there any tool or anything which I can do code optimization for wt.

Other than that, use a profiler (like valgrind ---callgrind) to see what is taking CPU.

How to make my Wt application run faster on slow internet connections?

Make sure gzip compression is enabled (built-in httpd does that, but when using FastCGI, this needs to be configured in web server).

How to automatically restart a Wt application running on Wt built-in http server after a seg fault is occured.

We use a little tool 'monit' for that.

I want to run my application on top of wthttp application but it should be available under the link

http:localhost/wt not as http://localhost:1001/

Use --deploy-path=/wt and --http-port=80

Or you may want to put the built-in httpd behind a reverse proxy such as HAproxy.

Does running Wt as built-in http will increase the performance than running as wtfastcgi?

There are a number of things that built-in httpd does better, and out-of-the box (asynchronous I/O, websockets, compression).

In the end it shouldn't make that much difference though.

Regards,

koen

    (1-1/1)