Disk Writes



  • Hello, I used Vivaldi for some month now. It's really a fine browser. I never recognized any problem. But after using an new notebook I had more and more problems with the msata 850 evo SSD. A few days ago I got a warning form Crystal Disk Info that the temperature of the disk growed over 50 deg. So I looked what was going on there and found that Vivaldi wrote 100th of megs into my user folder (AppData, endless loop). May be a bug I thought and stopped. In sum it wrote >30 GB. For the next time I planned to observe Vivaldi's behaviour. I didn't find any scenario where Vivaldi writes endless. But something I found: Every reload of a web page - may be a small one without big images - leads to 3-4 MB disk writes. Is there an explanation for this behaviour? Regards, Jo



  • @JosBrowser:

    But something I found: Every reload of a web page - may be a small one without big images - leads to 3-4 MB disk writes.

    Is there an explanation for this behaviour?

    Yes, this is how Chromium works (and Vivaldi is based on Chromium): First it saves the complete web page to the disk, then loads it from disk again to render it. There is nothing you can change about that.



  • Hi jtsn,

    No chance to save this in RAM?

    Regards,
    Jo


  • Vivaldi Translator

    Quite interesting.
    @JosBrowser:

    No chance to save this in RAM?

    Theoretically yes. If not rewrite the principles of how Chromium work, maybe it's possible to start some kind of RAM disk and the folder, where Vivaldi loads webpages, link to the RAM disk. Then all data will be forwarded to the RAM without need to rewrite anything. And the life of SSD could be a bit longer.



  • you can set up RAMdisk for Temps and then you can redirect Vivaldi caches there - VERY helpful in my opinion :)
    add this line (obviously dir is your desired target directory) to Vivaldi shortcut launcher (either on your desktop or taskbar etc..):
    –disk-cache-dir="T:\Temp\Vivaldi"



  • I have the whole vivaldi (app+data+cache) installed in a ramdisk, then I save its 1GB image before shutting down the PC.

    My ssd tanks, and vivaldi is blazing fast.

    Anyway excessive disk traffic can be due to the topsites file, it was created before the fixes. Is well worth to delete it (then you have to refresh all your thumbnails)



  • I have the whole vivaldi (app+data+cache) installed in a ramdisk, then I save its 1GB image before shutting down the PC.

    this means you are saving all the mess before shutdown,
    my solution above is elegant the way it gets totally flushed every shutdown so it's not getting more and more messy :)



  • Of course, you could use a cleaner (such as CCleaner or Wise Disk Cleaner) to clear all vivaldi cache, cookies, saved data, etc.
    That would keep your drive clean and prevent any unnecessary data from taking up valuable disk space….
    You could also you a disk defragmenter to defragment your disk (don't do it more than once a month though) ;)

    Hope that helped~ :)



  • Oh, and what version of vivaldi are you using? (beta or snapshot)
    Try updating to the latest snapshot: https://vivaldi.net/en-US/teamblog/100-snapshot-1-0-435-26-fixes-for-bookmarks-youtube-private-mode-and-stacked-tabs
    It might fix your problem~ ;)



  • @tzzsmk:

    this means you are saving all the mess before shutdown,

    The image written is as big as the ramdisk, no matter if you have the cached files inside or not.

    Anyway you can use a different solution, like the sync-toys under windows or rsync under linux to sync the files instead of operating at block level, and you can exclude whatever you want from the sync process.

    You can also script the cache clean before saving the image.

    Las but not least, you can use two (smaller) different ramdisks, one "permanent" for the app, the other, not saved, for the cache. Using the commandline switch you suggested.

    in short is the RAMdisk solution which is elegant, the details are details, they are up on user's preferences and skills.


Log in to reply
 

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.