# Energy Consumption of Web Servers: A Comparison Between Dynamic and Static Approaches
This repository contains the code, configurations, and experiment data for the thesis **"Energy Consumption of Web Servers: A Comparison Between Dynamic and Static Approaches"**. The study investigates the environmental impact of various web hosting strategies by analyzing different setups using **WordPress** and **Flask** applications deployed with **Apache** and **Nginx** servers.
---
## Getting started
## 📚 Thesis Abstract
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
The growing use of digital services has raised increasing concerns regarding the environmental impact, most notably the energy usage, of web hosting. This thesis examines the energy efficiency of different web hosting approaches (**static**, **dynamic**, and **cached**) for different applications using WordPress and Flask-based sites hosted on Apache and Nginx web servers. Additionally, a new approach is proposed for building a static version of a Flask-based application upon database changes.
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
Four test cases were compared:
## Add your files
- A basic WordPress application
- A Flask blogging application:
- With only GET requests
- With POST requests
- With authentication
-[ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
**Key Findings**:
-[ ] [Add files using the command line](https://docs.gitlab.com/topics/git/add_files/#add-files-to-a-git-repository) or push an existing Git repository with the following command:
```
- Static implementations consistently consumed the least energy and achieved the highest throughput.
cd existing_repo
- Cached solutions are effective when static deployments are infeasible but perform poorly under active user scenarios (POST/authentication).
- Dynamic rebuilding upon DB updates is efficient when updates are infrequent.
git branch -M main
- Nginx generally outperformed Apache in energy efficiency and request handling.
git push -uf origin main
```
## Integrate with your tools
---
-[ ] [Set up project integrations](https://forge.uclouvain.be/ArnaudJungers/web-server-energy-comparison/-/settings/integrations)
## 🗂 Repository Structure
## Collaborate with your team
```text
.
├── config/ # Configuration files for Apache, Nginx, PowerAPI, and system settings
├── results/ # Experiment results gathered from Grid'5000 (G5K)
├── scripts/ # Scripts for running experiments, generating graphs, and initializing nodes
├── site/ # All tested websites implemented in Flask and WordPress
└── README.md # Project overview and usage
````
-[ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
---
-[ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-[ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
Use the built-in continuous integration in GitLab.
To run the experiments and scripts in this repository, you will need:
-[ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/)
* Python
-[ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
* PowerAPI
-[ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
* Nginx and Apache web servers
-[ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
* WordPress
-[ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
* Flask
* npf
* Grid'5000 access (optional but used in the original tests)
***
Additional dependencies are listed in `scripts/requirements.txt`.
# Editing this README
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
## 📊 Results
## Suggestions for a good README
All benchmark results and figures are saved under the `results/` directory. These were generated on Grid'5000 gros nodes. To have the pdf for the results run the bash script `graphs.sh
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
## Name
Choose a self-explaining name for your project.
## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
