diff --git a/articles/advanced/benchmarks.md b/articles/advanced/benchmarks.md
index f134eb0..ef7adbc 100644
--- a/articles/advanced/benchmarks.md
+++ b/articles/advanced/benchmarks.md
@@ -8,42 +8,47 @@ Benchmarks
 A number of benchmarks have been done with PiNet stacked up against standard Raspbian off an SD card.   
    
 The tests use PiNet running on Ubuntu 14.04 on a fully gigabit (10/100/1000) ethernet network. They should be similar on a 100mbit network if the server is connected to the main switch via a gigabit port (also known as a stacking port).   
-The local SD card image is running a clean Raspbian 2014.01.07 with the test applications installed.   
-I am running only 1 Raspberry Pi on the network so loading time between NFS and NBD should be similar.   
-For PiNet there are 2 modes it can be run in    
-**1. NFS mode** - NFS is an older network technology. It is uncompressed and so any change made to the master operating system is live on the clients. It is good for testing and monitoring the exact amount of data needed to be loaded for a test to run. It is not recommended for production use due to it being slower than NBD mode. Do not use for more than 8 Raspberry Pis at one time!   
-**2. NBD mode** -  Uses NBD and squashFS compression to compress the operating system beforehand. After every change to the master operating system, the OS must be recompressed, which takes roughly 5-10 minutes. It is recommended for production use. The compression normally involves the amount of data cross the network dropping to roughly 40% of what NFS mode uses making it very useful for slower networks or networks running 8+ Raspberry Pis.   
+The local SD card image is running an unmodified Raspbian Jessie 2016.02.26 with the test applications installed.   
    
-The tests were completed on a Raspberry Pi model B revision 2 and the SD card used in these tests was a class 10 SanDisk Ultra card rated at 30MB/s.
+The tests were completed on a Raspberry Pi model B+, Raspberry Pi 2 Model B and Raspberry Pi 3 Model B and the SD card used in these tests was a class 10 Kingston card rated at 30MB/s.
 ## Results
-#### Boot to login
-Test | SD card | NFS | NBD (with compression)   
-----|----|----|----   
-Time | 35s* |66s| 63s   
+#### Boot to login (or to desktop in standalone card case)
+Test | PiNet | SD card
+----|----|---- 
+Pi 1B+ | 49s | 42s    
+Pi 2B | 20s | 20s   
+Pi 3B | 18s | 18s   
 
-#### Open Libreoffice Writer   
-    | SD card | NFS | NBD (with compression)   
-----|----|----|----   
-Time | 15s |24s| 20s   
-Data crossing network | N/A |75mb| 28mb   
+#### Login to desktop from login screen
+Test | PiNet | SD card
+----|----|---- 
+Pi 1B+ | 45s | N/A   
+Pi 2B | 11s | N/A   
+Pi 3B | 12s | N/A   
 
-#### Open Chromium web browser   
-    | SD card | NFS | NBD (with compression)   
-----|----|----|----   
-Time | 13s |20s| 12s   
-Data crossing network | N/A |45mb| 30mb   
+#### Open Libreoffice Writer   
+Test | PiNet | SD card
+----|----|---- 
+Pi 1B+ | 29s | 27s   
+Pi 2B | 12s | 11s   
+Pi 3B | 9s | 9s    
 
 #### Open Scratch   
-    | SD card | NFS | NBD (with compression)   
-----|----|----|----   
-Time | 6s |7s| 6s   
-Data crossing network | N/A |4.7mb| 3.6mb   
+Test | PiNet | SD card
+----|----|---- 
+Pi 1B+ | 14s | 12s   
+Pi 2B | 6s | 6s   
+Pi 3B | 4s | 4s   
 
-#### Open Sonic-Pi version 2 RC3   
-    | SD card | NFS | NBD (with compression)   
-----|----|----|----   
-Time | 37s |42s| 36s   
-Data crossing network | N/A |11.2mb| 11.1mb   
-   
+#### Open Sonic-Pi 2.9
+Test | PiNet | SD card
+----|----|---- 
+Pi 1B+ | 47s | 42s   
+Pi 2B | 20s | 20s   
+Pi 3B | 16s | 16s  
 
-*This is with boot to desktop enabled as LTSP loads a graphical login window.   
+## Conclusion 
+As can be clearly seen int he data, on many occasions booting from the local SD card is faster, especially with the old Raspberry Pi 1 Model B and B+. But, when you get to the Raspberry Pi 2 Model B and Raspberry Pi 3 Model B, the difference is barely noticeable with any of the applications.   
+Is important to keep in mind, PiNet is more though about saving time in management of the Raspberry Pis and less so about optimising individual Raspberry Pi speeds. The amount of time wasted for example swapping cards between classes alone usually negates any speed improvements with standalone cards, let alone having to keep them up to date and backed up.
+   
+This page was last updated on 4th March 2016.