Beiträge von alexxcons

    Found it a bit cumbersome to configure/maintin a docker container just to get syncthing running on my OMV (6.0.19-2 (Shaitan))


    Actually for me, it worked fine without docker, following this guide.


    An extra-step I did was creating a new user first, in order to don't run syncthing as root. In short, do the following:


    Code
    apt-get update
    apt-get install syncthing
    adduser syncthing-user
    systemctl enable syncthing@syncthing-user.service
    systemctl start syncthing@syncthing-user.service
    su syncthing-user
    nano ~/.config/syncthing/config.xml


    In the ~/.config/syncthing/config.xml of that user, I modified the XML Element gui in order to access syncthing via the web frontend. I just put in the server ip-address and set some user/pw for login:

    Code
    <gui enabled="true" tls="false" debugging="false">
      <address>192.168.178.23:8384</address>
      <user>admin</user>
      <password>MySecretPassword</passworrd>
      ....
    </gui>


    Afterwards sudo systemctl restart syncthing@syncthing-user.service and the web API is accessible from within my local network, and I can configure syncthing to my personal needs \o/.

    Zitat

    you can find only animations are being used that browsers can execute very cheaply (position transform, scale transform, opacity) as long as there is hardware-acceleration.


    So you want to make hardware accel a requirement for using the omv-webgui ? (Actually I am using a GPU .. though maybe as well that GPU is too old for a 100s animation ? What about smartphones, or other weak devices ?).


    From the Article you linked:

    Zitat

    Styles that affect pain

    ..., background-position, background-image, ...


    If you animate any of the above properties the element(s) affected are repainted, and the layers they belong to are uploaded to the GPU. On mobile devices this is particularly expensive because CPUs are significantly less powerful than their desktop counterparts, meaning that the painting work takes longer;


    Possibly your article already points at the problem in the omv code ... probably better to dont put an animation on the background-image, but rather put the image into some div, and do the animation there to prevent excessive repaints.


    Zitat

    I think your old hardware or some misconfiguration could be the issue. But this is clearly not a bug. Maybe some browser extension like this one can help you.


    Well, so far websites I visit dont do heavy (100seconds !) anymations, with the omv site as an exception. Though I might need to go that way, if more websites decide to show cosy animations and other resource-hungry bloat, instead of just showing me the content.

    Sorry, but I think you dont get my point. My point is, with all 3 systems I can visit hundreds of webpages without having any issue. But when I visit the page of my omv server, the CPU goes 100% for a minute on 3 different systems. That has a very bad smell to me.


    > . I blame the very old version of Debian 8 ...


    Sorry, I confused the debian version numbers. I am using Debian 12 (bookworm, testing) on the Phenom II and Debian 11 (Bullseye, stable) on the Travelmate ... I will fix all my postings accordingly. Sorry for the fuzz.

    I think the problem is not OMV because this is only a simple CSS animation/transition; i see the problem in the browser or the hardware of the client that does not support hardware acceleration which is considered standard today.

    Well, it happens on 3 different systems, all using hardware accel (youtube is regulary used by my kids) and it does not happen with any other website I regulary use. If my hardware can play youtube with 1024p while keeping respinsiveness, imo the hardware should be pretty much able to show such small animation without lag.


    Maybe the design of the web-frontend somewhat is the problem ... I dont know. In any way, meanwhile I am pretty sure that OMV is to blame here.

    What CPU/GPU are you using? I'm using a almost 11yr old Celeron (just using the onboard GPU, intel something or other).

    Hmm, than it seems to be something else. I can now reproduce on 3 different systems:


    1. Debian 12 (bookworm), AMD Phenom II X4 955, / GeForce GT 710 (~12 years old)
    2. MXLinux 21, AMD E2-2000 with onboard GPU (~9 years old)
    3. Debian 11 (bullseye), Acer Travelmate 5742Z with 2 Ghz Pentium (P6200) and onboard graphics (~10 years old)

    The lag in Firefox interestingly does not happen on the MXLinux machine (maybe firefox vs firefoxESR)... though it still shows 100% CPU for some time (until the animiation was shown 5 times .. which takes something like 1 minute)


    Imho a checkbox to toggle the animtaion on/off would be great ... I can imagine that such effects anyhow are not welcome by everybody. Should I open an issue ?

    Thank you for helping !


    Upgraded to 6.0.15-1, rebootet the omv server, cleared the firefox cache, pressed ctrl-shift-R., but still >100% CPU and lag for > 1minute here with firefox.


    I "think" I can now type the user/pw a bit more fluent, though in firefox.


    Just took another try with chromium, and found out that it actually as well eats 100% CPU, but divided into two processes. However unlike firefox, it keps beeing responsive.


    Suppose you need some old CPU/GPU, like mine, to fully reproduce the problem ;)

    Using chromium that does not happen. Looks like it is not possible to disable the animation in OMV :(


    Not sure if OMV or firefox is to blame. I can reproduce the issue on different maschines.


    I dont know of any other website for which that happens, so I suppose OMV at least could be improved here.


    OMV Version: 6.0.10-1 (Shaitan)

    Firefox Version: 91.6.0esr (64-bit)

    OS: Debian 12 bookworm (testing)


    On slow maschines, entering user/pw is hardly possible during the animation.


    Does that happen only to me ? Any ideas would be welcome !


    Edit: As well happens for chromium ... though chromium balances the load on two separate processes and keeps beeing responsive.