# Disabling dietpi-boot service? **URL:** https://dietpi.com/forum/t/disabling-dietpi-boot-service/1462 **Category:** General Discussion **Created:** [19 August 2017 06:10 UTC](https://dietpi.com/forum/t/disabling-dietpi-boot-service/1462 "2017-08-19T06:10:48Z") **Posts on this page:** 1 **Showing post:** 16
### Author: ![k-plan](https://dietpi.com/forum/user_avatar/dietpi.com/k-plan/32/12_2.png) [@k-plan](https://dietpi.com/forum/u/k-plan) #### Post date: [15 October 2017 15:58 UTC](https://dietpi.com/forum/t/disabling-dietpi-boot-service/1462/16 "2017-10-15T15:58:36Z")
> [@NJS](#): > > Interesting, why is that? As far as I noticed, many networking functions a directly implement into the kernel. So, if you will disable functions by config, it will not speed up things, it will cause only time lag. Have tested to disable IPv6 support and it will increase boot time. > [@NJS](#): > > In my case I don’t even initialize WLAN until later from within my App. I will say, it’s not a good idea. Better let’s Debian/DietPi do this for you, if boot time is important. If you will set it after boot-up, you have to wait for reinitialize the hole network stack. > [@NJS](#): > > I wonder if I could remove the network manager entirely from the boot sequence and load it later when needed. Hmm, DietPi does it in the [old Debian style](https://www.debian.org/doc/manuals/debian-reference/ch05.en.html) with a single config file. I personally like this much more then using a network manager or the Rasbian way. Sense of speed, DietPi approach is a good to go. > [@NJS](#): > > Just curious, what is the problem with this (I’ve seen it suggested in many places)? Have tested it. In some rare chases, with tweaked sd card settings, it will fuckup the hole overclock setting on some of my RPi devices. In short, it only make sense to set SDRAM schmoo to get more than 500MHz SDRAM frequency (default is unset). And bullshit is all over the internet. Many people creating content only by copy-and-paste without trying it seriously out or understand the background. Here some good informations, but always keep a eye on it, you have a RPi Zero and not a RPi 3 or RPi 2: > **[GitHub - aikoncwd/rpi-benchmark: Script to run some benchmark test for Raspberry Pi](https://github.com/aikoncwd/rpi-benchmark)** > > Script to run some benchmark test for Raspberry Pi > **[Home](https://github.com/RetroPie/RetroPie-Setup/wiki/)** > > Shell script to set up a Raspberry Pi/Odroid/PC with RetroArch emulator and various cores - RetroPie/RetroPie-Setup > [@NJS](#): > > I am using Samsung EVO+ 32GB, which I specifically selected to reduce boot time since it is supposed to be one of the fastest available. It’s the picky sd card I ever own. With some devices this card will not boot up (timing problem on Odroid C1 and C2). And the speed is only at the very most ordinary. I don’t use Samsung EVO+ in my SBC any more now. For mobile phone, as storage device, it will be okay. So all my get in there. > [@NJS](#): > > After adding dtoverlay=sdhost,overclock\_50=84 to \DietPi\config.txt read speed increases modestly to 28 MB/s but boot time is still over 26 sec (and the Pi Zero W onboard wifi stops working) It correct. It the wrong parameter and the wrong overlay for newer kernel. > [@RPi | Double SDcard IO (Read/Write speeds)](https://dietpi.com/forum/t/rpi-double-sdcard-io-read-write-speeds/279/1): > > I love Raspberry Pi’s and I have been using them for years. Its also the very 1st DietPi image I created. One of my major gripes with the RPi, is the limited performance of the SDcard IO (read and write) speed: This is a known limitation with all Raspberry Pi’s and only 17.5mb/s read and write can be achieved. Whereas, other SBC’s (eg: Odroid C1/2) can offer SDcard IO performance at 40+mb/s You can double the read and write performance to 35mb/s on all Raspberry Pi’s: Ho… ```plaintext ##---SD-CARD_Overclock_(RPi3,RPi2,RPiZero)------ dtoverlay=sdtweak,overclock_50=100 ``` And please have a look at the output of: ```plaintext root@RPi-Zero_W:~# dmesg | grep mmc .... [0.823936] mmc-bcm2835 20300000.mmc: could not get clk, deferring probe [0.974521] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1) [0.980984] mmc-bcm2835 20300000.mmc: mmc_debug:0 mmc_debug2:0 [0.984939] mmc-bcm2835 20300000.mmc: DMA channel allocated [1.092000] mmc0: host does not support reading read-only switch, assuming write-enable [1.098577] mmc0: overclocking to 100000000Hz [1.102668] mmc0: new high speed SDHC card at address aaaa [1.111696] mmcblk0: mmc0:aaaa SE32G 29.7 GiB ..... ``` ## so you can see, if it work correct with your sd card. \ > [@Fourdee](#): > > 100ms only for SD card overclock. Would of expected more, maybe only benefits multi-core RPi’s. Hmm. Yes correct. On RPi2 and RPi3 (multi-core) it will be work much better. And if you have a huge swapfile like in default config, you will get a significant drop on boot time. But the main goal is overall system performance and response. BTW: - have you notice the typo in dietpi-config dialog and dietpi.txt? ![171015-0006.gif](https://dietpi.com/forum/uploads/default/original/1X/a9c3fb719984f7b40d87295c83950ee77956bef6.gif) ![171015-0003.gif](https://dietpi.com/forum/uploads/default/original/1X/09269648fcff4e5b40dfee71f01d5eae71f62a4a.gif) ```plaintext # >> Misc Options ----------------------------------- #Size of dphys-swapfile to generate (MB) # 0=Disabled | 1=auto (1GB-RAM = size) | 2+=manual Swapfile_Size=1567 ``` 😉 Don’t think to make a github issue for this. 😃 --- _[View the full topic](https://dietpi.com/forum/t/disabling-dietpi-boot-service/1462)._