• Register
    • Login
    • Search
    • Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    Image Compression Association

    Feature Request
    4
    8
    2221
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      need2 Moderator last edited by

      It would be nice to have an option to associate different compression levels with either hosts, groups, or images. That way if/when you are needing to image a system that has crap for processing performance you can associate it with a lower compression level, allowing it to finish the task more quickly at the cost of disk space on the storage node. Yes, you can currently adjust the system wide compression level, but this effects every task running (that uses the compression obviously).

      I am not sure on the feasibility of this, and ideally this wouldn’t be a long term issue since we should all be throwing systems with Atom (and similar) processors down a flight of stairs.

      1 Reply Last reply Reply Quote 0
      • N
        need2 Moderator last edited by

        Alright, that answers that. I appreciate the consideration.

        1 Reply Last reply Reply Quote 0
        • Tom Elliott
          Tom Elliott last edited by

          Adding the capability isn’t an issue by itself but it would only work for images as that’s the item that gets compressed. It would, also, only be viable for the upload. For this reason, it’d be recommended to adjust the global setting unless you’re uploading multiple images at the same time. I doubt this is the case. So, in my highest opinion, adjusting this value to quicken the upload of a problematic machine isn’t that difficult. Besides that, once it’s uploaded, the deploy should be faster. That and better compression on upload means less data to transfer during download.

          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

          Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

          Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

          1 Reply Last reply Reply Quote 0
          • N
            need2 Moderator last edited by

            Fair enough. The one problem machine was going to take 4+ hours for about 15 GB, and I know this is an odd case.

            1 Reply Last reply Reply Quote 0
            • B
              BPSTravis Developer last edited by

              My uploads run about an hour on full compression on any of my machines, but it then allows for 11-13 minute deployments.

              It’s worth the wait so i’d leave the compression maxed unless there is some reason you need to upload faster.

              You only upload once in a great while, you deploy regularly.

              [SIZE=12px]signature:[/SIZE]
              [QUOTE]I think I know things, but I really don't. You shouldn't follow any advice I give. - BPSTravis[/QUOTE]

              1 Reply Last reply Reply Quote 0
              • V
                VincentJ Moderator last edited by

                The problem I can see is that unless you can change the compression level on the server after upload. you would need to upload multiple times to be able to suit those hosts with a different compression level.

                How long is your ‘crap’ machine taking to upload?

                1 Reply Last reply Reply Quote 0
                • N
                  need2 Moderator last edited by

                  Yes, typically you would want a decent machine to be your original image host, so that the whole process gets done faster for you. But there are situations like doing a pre-service backup with Fog on a crap machine where a better processor isn’t an option.

                  Clearly, this is not a dire need, but it would speed things up in a few situations. It also shouldn’t affect the default workflow for users if the default setting is to use the system-wide compression level setting.

                  1 Reply Last reply Reply Quote 0
                  • V
                    VincentJ Moderator last edited by

                    Could you just use a powerful PC for uploading?

                    I’ve not had problems with the download being extremely slow…

                    1 Reply Last reply Reply Quote 0
                    • 1 / 1
                    • First post
                      Last post

                    229
                    Online

                    10.4k
                    Users

                    16.4k
                    Topics

                    150.6k
                    Posts

                    Copyright © 2012-2023 FOG Project