HomeVeloRAM

Ram based caching software. Speeds up HDD and SSD based storage.

Very slow shutdown... Messages in this topic - RSS

inetdude
inetdude
Posts: 14


3/15/2019
inetdude
inetdude
Posts: 14
Hello,

I installed VeloRAM 3.0.0.1 some days ago... Bevor I installed VeloRAM I had in average ca. 30 sec. when I initiate system shutdown.


Win10 64bit +
32 GB DDR3-RAM +
2 SSDs (128 GB + 240 GB) SATAIII +
1 HDD (2 TB) SATAIII +
MSI UEFI BIOS dated March 2018
--> Secure boot is not present

Very positiv is that restarting the PC (after drives update or after new software requiring system restart) has become very quick... First I thought the RAM would be emptied so there were no caches when restarting, but it seems the caches will persist even when rebooting!

MY PROBLEM IS NOW:
--> After installing VeloRAM I am experiencing now shutdown times from 120 sec. and above!!!

What is wrong???
0 link
inetdude
inetdude
Posts: 14


3/17/2019
inetdude
inetdude
Posts: 14
Don't know what happened...

Yesterday in the morning I hat a BlueScreen (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED) and after that the shutdown times from Win10 became "normal" - nearly 30 sec. with active caches for 4 volumes (using VeloRAM).

Is there an explanation on this? ;-)
0 link
inetdude
inetdude
Posts: 14


3/18/2019
inetdude
inetdude
Posts: 14
And again I still have the problem - last Win10-shutdown was longer than 1 min. 15 sec. !!!

Will not buy the product until I have a satisfactory answer to my problems...
0 link
bodo
bodo
Administrator
Posts: 98


3/18/2019
bodo
bodo
Administrator
Posts: 98
>Very positiv is that restarting the PC (after drives update or after new software requiring system restart) has become very quick... First I thought >the RAM would be emptied so there were no caches when restarting, but it seems the caches will persist even when rebooting!


it not persistant for good reason:

saving and loading all that memory takes its time. It could possibly speed boot when read in 1 part instead of 5000 parts, some only a few sectors long. Windows 10 has optimized boot sequence.


The long shutdown may be an issue we need to collect data to see when it happens.


But we know the source and there is no shutdown specific process that takes place and uses ab so much time.
It could be that it waits for something though. But are you sure you have no other software running that is responsible. ?
edited by bodo on 18.03.2019
edited by bodo on 18.03.2019
0 link
inetdude
inetdude
Posts: 14


3/18/2019
inetdude
inetdude
Posts: 14
bodo wrote:
it not persistant for good reason:

saving and loading all that memory takes its time. It could possibly speed boot when read in 1 part instead of 5000 parts, some only a few sectors long. Windows 10 has optimized boot sequence.
--> I don't understand, my english is not good enough... Is the RAM-cache of the volumes deleted when shutting down or restarting the pc? Has it not to be stored to the drives first otherwise data would be lost?

As I write this I remember of my RAM usage being at 70% (I have a system monitor running in the background). This is nearly 23 GB RAM. The maximum RAM usage I experienced in the past (before installing VeloRAM) was 11 GB (but mostly between 6 and 8 GB).

So at this moment there was at least 23-11 = 12 GB in Cache (= RAM)! --> If (at system shutdown) this 12GB have to be stored to the drives first (I have 2 SSDs + 1 HDD with 2 volumes) how long does it take to get this done?

bodo wrote:
It could be that it waits for something though. But are you sure you have no other software running that is responsible?
--> At least I did not install new software after installing VeloRAM! And I did not have this problem before, say there were no conflicts before... So if there is now a conflict with other software running, the only thing that changed is VeloRAM!

Is there a possibility to track software conflicts in win10 to find out?
0 link
bodo
bodo
Administrator
Posts: 98


3/18/2019
bodo
bodo
Administrator
Posts: 98
I try to easy explain:
If you write really much and shutdown then it needs to
write that whole stuff to the disk first before it shutsdown.
That can take time, all software with write caching has this behaviour I guess.
That is our answer to the original question of this post.
0 link
inetdude
inetdude
Posts: 14


3/19/2019
inetdude
inetdude
Posts: 14
bodo wrote:
...needs to write that whole stuff to the disk first before it shutsdown.
That can take time, all software with write caching has this behaviour I guess.
Yes, I think this is the right explanation... Toast

I will do some tests the next days, because I do not only have 2 SSDs (with VeloRAM cached) and 1 HDD with 2 Volumes (ohne of them also with VeloRAM cached), but also a "RAM Disk" already installed some months ago.

And my impression is even the cached HDD volume (with VeloRAM) is faster than the RAM-Disk... If this is the case, I wouldn't need anymore the RAM-Disk!

Is there a possibility to upload some screenshots to the threads of this forum? wink
0 link
bodo
bodo
Administrator
Posts: 98


3/19/2019
bodo
bodo
Administrator
Posts: 98
You can embed urls, I don´t know of a direct way.
0 link
inetdude
inetdude
Posts: 14


3/20/2019
inetdude
inetdude
Posts: 14
Now I made some tests to compare disk performance between RAM cached disks (with VeloRAM: volumes c, d, e, f) and my older RAM-disk which I created almost a year ago (created with ImDisk Toolkit: volume r).

The volumes c and d are two SSDs (128 GB and 240 GB) - volumes e and f are on the same HDD (2 TB). Volume r is a "virtuell" disk (8 GB) installed into the RAM (used for system and user temp folders, win10 update folders, browser temp folders, temporary internet folder, etc.).

Here are the results:

1. Performance of HDD (volume f):
https://halln7zz-my.sharepoint.com/:i:/g/personal/r5560_365office_co/EVbWu71pcIFCkiLy4iXBC3MBTC-60prgOpfsAAU9H53y_A?e=R0i4bz

2. Performance of SSD (volume c): system volume...
https://halln7zz-my.sharepoint.com/:i:/g/personal/r5560_365office_co/EfdMUNFVsEBPvG40v2W0FgIBBHxrKYaYJP-sFaQlq4PdqA?e=flztLj

3. Performance of RAM-Disk (virtuell volume r):
https://halln7zz-my.sharepoint.com/:i:/g/personal/r5560_365office_co/EYgCtl306zdJt8C2_RTBaFUBMtugwL2hsj24lQY4tc6CXQ?e=YAw9BN

==> The performance of the HDD is equal to the SSD...
The reason is very clear: both are cached with VeloRAM, so in fact the system is using the RAM to read/write data and not the physical disks!

==> Performance of HDDs/SSDs is 57 % better than the RAM-disk...
Although both VeloRAM cache and RAM-disk are using the same system RAM, there must be something reducing the performance of the ram disk (there must be some kind of "overhead" creating a virtuell disk in the ram)!

CONCLUSION:
I decided to turn back all the settings I changed in Win10 (to have better system performance using the ram disk) to their origin. Performance using VeloRAM (using a ram cache to read/write data instead the physical drives) is not only much better, there is also a reduced access to the physical drives, because not all data in the cache needs to be writen to the SSDs/HDDs!

(I hope the links to the pictures will work fine...)
0 link