Cookies Consent Page. Project Peach Light Background Logo.
We use cookies to enhance your browsing experience. By clicking 'I Understand and Accept', you consent to our use of cookies.
I understand and accept
No, I don't want to use cookies
My Account
Control Panel
An example toast message
Do Something
Login
en
en
Header. Project Peach Dark Background Logo.
Menu
en
en
Change Language
Login
My Account
Control Panel
What's It About?
Try It
About Us
Contact Us
Book A Demo
Buy a Website Now
Log Out
Login
Login
en
en
Do Something
Login
en
en
Header. Project Peach Dark Background Logo.
Menu
en
en
Change Language
Login
My Account
Control Panel
What's It About?
Try It
About Us
Contact Us
Book A Demo
Buy a Website Now
Log Out
Login
Login
en
en
Do Something
Login
en
en
Header. Project Peach Dark Background Logo.
Menu
en
en
Change Language
Login
My Account
Control Panel
What's It About?
Try It
About Us
Contact Us
Book A Demo
Buy a Website Now
Log Out
Login
Login
en
en
Do Something
Login
en
en
Header. Project Peach Dark Background Logo.
Menu
en
en
Change Language
Login
My Account
Control Panel
What's It About?
Try It
About Us
Contact Us
Book A Demo
Buy a Website Now
Log Out
Login
Login
en
en
How close to carbon neutral can a website be...

Website Energy Efficiency And Carbon Emissions

Let's review Peach Rocks web application design and hosting in contrast to a conventional, well established website hosting company like GoDaddy.
Try It Right Now!
Book A Demo

Peach Rocks

Carbon Neutral Websites
Over 99% Less Energy
Over 99% Less CO2
Offset 99% Less Trees
Download our interactive business plan, profit and carbon efficiency Excel spreadsheet
Click Here

Peach Rocks

One Website per Year
Energy: 1.67kW / 84p1
CO2 Emitted: 309g
Offset: 1 tree / 78 years
1 Figures based on a single Windows 2016 server hosting 1,500 websites.

GoDaddy

One Website per Year
Energy: 699kW / £3491
CO2 Emitted: 135kg
Offset: 5 trees / 1 year
1 Figures obtained for GoDaddy based on the carbon offset of hosting one website.

Peach Rocks And Energy Efficiency

Our Hardware, Software And Hosting Example
Overview
Working with our partners MedicineChest Ltd and The Pharmacy Centre we host and manage about 1,500 UK based pharmacy websites and their associated patient prescription ordering on a single Microsoft Windows 2016 server. Each pharmacy has on average 500 patients with repeating prescriptions containing on average 3 items. Once every 28 days they will use our web application software by going on the website and ordering their prescriptions.
So that’s 750,000 visits per month simply for prescription ordering. Each pharmacy has an average of 4 employees that manage these prescriptions and use the system on a daily basis to manage the patient medication management. There are also the online ordering visits for retail side of each website. We also have appointment booking for pharmacy services like flu jabs, medicine reviews, travel advice, etc. The performance and efficiency of our software solution means we can run more processing on a smaller server.
Our Server
We have a modest server configuration. Our single server is a XEON 3.5Ghz E3-1231 V3 4C/8T, 32GB RAM, 1TB SSD. It’s a modern server and it sits in a rack at a TeleData data centre in Manchester, UK. We chose this XEON and SSD combination to reduce power consumption and maximise our web application performance. The CPU typically tops out at 80W, although the motherboard can deliver 142W at peak performance.
Our SSD is considerably lower power consumption than an HDD with typical consumption below 9W. The motherboard power consumption averages 100W. Our single 32GB DDR4 memory module is around 3W. Peripheral cards like networking could add up to another 20W. The motherboard has built-in graphics and I/O.
CPU: 80W to 142W, SSD: 9W, Motherboard: 100W, Memory: 3W, Network Card: 20W.
Total: 212W or 274W load dependent.
Our Server Usage
In order to get a reasonably accurate power usage of our server we observed our CPU and networking performance for our web application in the list of tasks. During the typically busy morning periods our web application CPU usage averaged 15%, never exceeding a maximum of 30%. For the remaining normal usage, the CPU averaged 5%, not exceeding 15%. We also monitored the flowing network traffic for the web application, which is typically 2-4% network utilisation and never more than 10% for the server during the busy period. This is to be expected since we transmit minimum data across the wire.
Our web application is idle when not dealing with user messages that trigger events, yielding correctly to other Microsoft Windows processes which saves energy. Having reviewed the usage, we believe we are not exceeding 212Wh consumption for the entire server.
Our Environment
We host our server at an award-winning data centre in regards to energy efficiency. Teledata invested to create an environment which uses a 2MW smart energy storage system that powers the racks and cooling rather than a conventional, fluctuating mains supply with generator backup. The system can draw energy at the best times for the national grid and stop drawing during unusual events. Using battery storage carries a number of energy-saving advantages.
  • A low loss transformer is proven to save 8-10% of annually consumed kW h.
  • Intelligent switching regarding charging the batteries ensures that the greenest energy is used at times of least demand.
  • Voltage optimisation and regulation at 225V at transformer level reduces energy wastage and extends the life of data centre equipment by up to 40%. An indirect energy saving on equipment production and delivery energy.
  • Intelligently controlled cooling systems.
  • Cold aisle containment.
  • Under floor cold air channelling minimises wastage.
  • Variable speed fans within the A/C condenser units.
  • Free air-cooling systems.
  • Office space air conditioning controls to minimise wastage out of hours.
  • Highly efficient cooling pumps.
  • Cold aisle blanking throughout the facility.
This reduces our carbon footprint in regards to the ancillary operations needed for the day to day running of our racked server. Primarily, heavy energy consuming equipment like cooling which can typically add another 50% energy consumption to actual server power consumption. However due to Teledata’s energy saving efforts we can reduce this to 35% ancillary costs.
Breaking It All Down To Figures
Actual total server power consumption is 212Wh. 5.088kW/Day for the actual server. Ancillary costs @ 35% is 1.781kW/Day. Total server footprint 6.869kW/Day. Yearly total power consumption of 2,507kW, which is not dissimilar to the power consumption of a typical UK house over a year.
If the total energy consumption footprint of a single server is 2,507kW. According to 2022 GHG data, the CO2 emitted into the environment per kW h of electric consumption is 0.193kg. If we transform our server electricity consumption into GHG CO2 we get 484kg. If one tree on average absorbs 25kg of CO2, then we would need to plant just over 19 trees to be carbon neutral in our server activities per year. At £1 per tree, it would take £19 to become carbon neutral for our single server.
For a conventional website where one dedicated server hosted just one website/web application the above would be true. Simply plant 19 trees to achieve carbon neutrality. However, we host 1,500 websites on our single dedicated server. Let’s do some more calculations. If our total energy consumption for our single server is 2,507kW, then for a single website using our web application technology the total energy per year consumed is slightly over 1.6kW, which generates 0.309kg, or 309g of CO2 per year. To put this into perspective it would take about 81 websites before a single tree is needed to offset and become carbon neutral. The tree cost per website to achieve carbon neutrality is just over 1p for one website.
Our Pharmacy web application is more demanding than just a typical website. We could potentially host about 3,000 of this type of application on a single server. For a single server simply hosting websites, we could host many more, perhaps 5,000. For 3,000 websites this would push down our CO2 emissions even further to 154g and the need to plant one tree per 162 websites in order to be carbon neutral. Around ½p towards a tree to be carbon neutral.
Comparison To GoDaddy
Looking at Eleven Comm website hosted by GoDaddy, they estimated 135kg of CO2 annually. We can compare this using the information above to 309g CO2 for a single Peach Rocks website, being conservative and proposing sharing with 1,500 websites per dedicated server. It would be very easy to go carbon negative with just over 1% of a single tree.
We are 99.998% more efficient reducing CO2 emissions than GoDaddy per single website. Personally, I don’t believe the GoDaddy supplied emissions figure of CO2 is correct when reverse engineered to kW, it doesn’t scale up when you add more websites.
Let’s Take A Detour To The Client Side
We’ve been exclusively talking about server-side environment impact so far. What about the way the software is written that is delivered from the web server to the client browser. What additional, distributed costs could that impose? Remember this software in your client’s browser originated from the server. Should we discuss long polling to keep a web page up to date?
So, what exactly is long polling and why is it done? In a conventional website a web page is downloaded to the client and the connection to the server is then broken. Only a page refresh will get any subsequent changes to the data. Each web page request to the server costs 0.55mAh, or put another way you get 8,000 trips to the server per 1kW. Pressing the F5 key 8,000 times consumes a kW. Seems cheap? It takes more than one call to populate a page, each images requires one call. It could take 50 calls to populate a single page in one browser. In order to keep a page update with current information and to avoid visible web page roundtrips software could make an under the radar call several times per minute to ask if anything has changed on the server.
Consider a single user sat on FB (Facebook) for one hour. To receive regular updates FB long polls at say a rate of 4 calls per minute to find new postings and comments. Over the hour FB will make 240 calls under the radar. Given that it takes 8,000 calls to consume 1kW then 240 calls consume 0.03kW or 30W. Consider a busy website like FB, with say 1,000 users with the web page open in a browser tab. 4 calls per minute become 4,000 calls per minute, 240,000 per hour, 30kWh. That’s 5.8kg of CO2. So, in a little over 4 hours, we’d need to plant a tree to be carbon neutral. It’s much worse than this since we only considered a 1,000 connected web browser instances. We believe that if a server downloads the software, it should be included in carbon emissions.
Is there a better alternative? Yes, we designed our web applications to use a persistent connection from the client web browser to the web application running on the server. The impact is pretty sensational. Let’s consider the example above contrasted with one of our web applications. There is no longer any need for long polling since if anything changes on the server, we can simply push an update from the server to the client browser down the persistent connection.
Let’s consider during an hour open in a browser tab there are 4 data changes on the server that require an update to the user’s browser hosted web page. Since each change requires only a single direction push the power consumption halves to 0.275mAh. 4 calls equal 1.1mAh. That’s only 0.25W. It’s also better than this since each user’s browser only receives the data update relevant to what they are looking at, since push is smartly targeted. Put another way, there’s no standing charge to obtain updates as in long polling. Only the data updates that are needed are actually smartly pushed.
Therefore, how you design your software matters on a global scale!
However, This Isn’t All Of It…
We minimise our energy in a number of other ways that are difficult to calculate. Some of the measures below have added to our excellent power consumption and associated performance outlined in our calculated emissions. Some, however are around saving energy ‘off the server’ using our development techniques, processes, network traffic reduction and installation to name but a few.
Our Web Application Software Saves Energy Indirectly
  • Our web application software is built into native machine code that the CPU understands directly. This is a one-off build process. This contrasts directly with interpreted software like PHP (a common web development language). In this scenario the text-based PHP must be converted each time it is called by the web server into machine language. Say a PHP script is called 1,000 times in an hour, the script needs to be converted to machine code 1,000 times. 1 time/1 off Vs 1,000 times.
  • Network traffic reduction. We don’t use long polling and we utilise a persistent connection. Our messages are tiny, header-less, passing only the data required to fulfil the request. They are optimised to be either single direction, from client to server or from server to client or bi-directional if returning a response. In all cases we transfer bytes rather than kilobytes. We also use targeted updates, since we know which client browsers are looking at what page we only send to interested parties. For example, if 10 users are online, 2 are looking at the people page and 8 on the home page, if we make a change to the people page then only 2 update messages will be sent to observers of the people page.
  • Our webapps are of a single page design. This provides both smooth inter-page movement and energy savings. All the pages are download in just one HTTP request at initialisation and there are zero server roundtrips on moving pages.
  • What is the energy consumption with duplicate development? A website and multiple mobile apps? Different development teams with writing duplicate code for the same end result. Monitors, compilers, testing... All costs energy. There is just one solution with our web applications. Zero duplication.
  • Installation, updates and distribution. Same for both desktop applications and mobile apps. Consider the Microsoft Windows monthly updates in terms of data transmission, each and every desktop on longer as it's at shutdown. What about the play store and iTunes store? The updating, download and installation cycle. With live webapps there's a single web application instance in the cloud. Distribution is just like a website. Transparent to the user and minimal energy consumption.
  • We have one technology for both websites and apps. Internal corporate applications, front facing websites or end user applications. There's a single framework for all needs. Our bigger building blocks of code speed up development which is more human efficient and energy efficient.
  • What's the biggest waste of energy and resource from a programmer’s perspective? Hunting down badly worded bug reports? Our live webapps report errors from both the server and client components centrally. We get the exact line of failure. As users use, we fix. We've fixed the excessive energy in fixing bugs by making it much easier. Our users are indirectly testing our software 24/7 and our software improves in quality over time.
  • We've just one centralised cloud hosted webapp instance that ALL browsers connect to. There's no concept of an instance running per machine. Only our UX runs in browser, the browser is the client app instance. All the application running costs are server based, only the browser costs are on the client side.

Quick Fact Sheet – Server Only Data

1 Website Carbon Neutrality
Carbon Negative Page. Project Peach, Peach Only, Logo.
Peach Rocks
Environmental Impact of hosting a single website
  • Total Energy Consumption per Year: 1.67kW / 84p1 per Year
  • Total CO2 Emissions per Year: 309g2
  • Trees to achieve Carbon Neutrality per Year: 1 tree every 78 years per website3
Carbon Negative Page. GoDaddy Logo.
GoDaddy
Environmental Impact of hosting a single website
  • Total Energy Consumption per Year: 699kW / £349 per Year
  • Total CO2 Emissions per Year: 135kg4
  • Trees to achieve Carbon Neutrality per Year: Over 5 trees per website
1,500 Websites Carbon Neutrality
Carbon Negative Page. Project Peach, Peach Only, Logo.
Peach Rocks
Environmental Impact of hosting 1,500 websites
  • Total Energy Consumption per Year: 2,507kW / £1,253 per Year
  • Total CO2 Emissions per Year: 484kg
  • Trees to achieve Carbon Neutrality per Year: 19 trees per year
  • Annual Tree Cost for Carbon Neutrality: £19
Carbon Negative Page. GoDaddy Logo.
GoDaddy
Environmental Impact of hosting 1,500 websites
  • Total Energy Consumption per Year: 1,048,500kW / >1mW / £524,250 per year5
  • Total CO2 Emissions per Year: 202,500kg / 202.5t6
  • Trees to achieve Carbon Neutrality per Year: 8,100 trees per year
  • Annual Tree Cost for Carbon Neutrality: £8,100
Download our interactive business plan, profit and carbon efficiency Excel spreadsheet
  • 1 Based on 50p per kW h
  • 2 0.193kg of CO2 emitted per 1kW h
  • 3 A single tree negates 25kg CO2
  • 4 This CO2 emission figure given by GoDaddy; other values reverse engineered from this
  • 5 This shows how susceptible hosting providers are to increasing energy costs, see note #1
  • 6 We’ve no idea how GoDaddy arrived at 135kg CO2 per year but it doesn’t scale, costs Vs revenue
Back To: Home
Back To: Top
Coming Next: Partnerships
AI, NoCode, WaaS websites done right! We build the future of real-time websites and live mobile web applications.
Project Peach Limited
10520034
48 Buckton Vale Road, Carrbrook, Stalybridge, England, SK15 3JP.
(+44) 1904 349 316
Store Hours Unavailable
No store selected for opening hours
Loading Open Hours...
Do Something
Do Something
Do Something
Interested in our Affiliate Program? Just add your email address below
Send
What's It About?
Home
Our online solution is nothing like anything else you’ve experienced before. Read all about it.
The Product
10 Years of solid R&D, testing and in-production with real clients. A Solution that’s 10 Years Ahead.
The Features
Want to change your website on your website? How about right-click, edit in-place and save. That’s it!
The Solution
Your business changes on a daily basis, why shouldn’t your website? No skill required!
About Us
Our Team
Our experienced UK team have been designing, writing and maintaining complex software applications since 1983.
Our Company
We are a self-owned UK limited company, with no external investors and are a self-funded profitable business.
Our Clients
We have long term clients for variety of industry sectors, Corporates,  SMEs, Small Business and Affiliates.
Affiliate Programme
We're always looking for affiliates to sell our WaaS, AI, NoCode websites globally. Want to partner up?
Our Ethos
Carbon Neutral
A Sustainable Future.
Partnerships
Become an Affiliate or Partner.
Web3
The Future of Web3 Websites.
Try It Yourself
One Step At A Time
Go at your own pace. Let us guide you step-by-step in using our live edit of your website in-place.
Our Playground
Interested in how our live website updating works? Head to our interactive playground and play around.
Create Your Own Website
Just fill in a simple form and we will build you a trial website. It's a time limited full version. It's FREE and No Credit Card.
Try Our Online Store
Try out our online retail store? We've a retail store extension module that you can upsell to your clients.
Project Peach © 2011 - 2023
Cookies Policy
Privacy Policy
Terms and Conditions