Project

General

Profile

action #56594

Why would a worker host need to upload images to another machine when afterwards the image is only used on the same worker host?

Added by okurz about 1 year ago. Updated about 1 year ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2019-09-08
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

As ideas based on our investigation work in #54902#note-10:

Why would a worker host need to upload images to another machine when afterwards the image is only used on the same worker host? E.g. we have some jump hosts so we would not need to copy back and forth assets at all or in some cases we have a single worker machine for a matching working class. Would make sense to not down- and upload the file again to the same machine, potentially using the caching approach for uploading as well?

History

#1 Updated by coolo about 1 year ago

This is super unrealistic as it moves assets outside of the asset database and outside of the asset tracking, basically implementing a distributed storage.

Also available in: Atom PDF