diff --git a/doc/bugs/git-annex_is_slow_at_reading_file_content/comment_12_466a365bca48065cc6b9e280b5c385a5._comment b/doc/bugs/git-annex_is_slow_at_reading_file_content/comment_12_466a365bca48065cc6b9e280b5c385a5._comment new file mode 100644 index 0000000000..e7078e5a92 --- /dev/null +++ b/doc/bugs/git-annex_is_slow_at_reading_file_content/comment_12_466a365bca48065cc6b9e280b5c385a5._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="Atemu" + avatar="http://cdn.libravatar.org/avatar/86b8c2d893dfdf2146e1bbb8ac4165fb" + subject="comment 12" + date="2024-03-02T08:32:40Z" + content=""" +Thank you for looking into this again. + +> I'd rather avoid OpenSSL wrappers because adding a C library dependency on openssl will complicate building git-annex in some situations. + +Would it be possible to make this a build-time option perhaps? + +git-annex without SIMD hashing obviously still *works* fast enough for many purposes as its the status quo but having it would be a greatly appreciated optimisation by many. It'd be great to have the option to enable it wherever possible and simply fall back to non-SIMD where it isn't. + +> Also, whatever library git-annex uses needs to support incremental hashing, otherwise git-annex has to pay a performance penalty of re-reading a file to hash it after download, rather than hashing while downloading. + +Agreed. Incremental hashing is too important to lose over a general optimisation like this. +"""]] diff --git a/doc/forum/New_external_special_remote_for_rclone.mdwn b/doc/forum/New_external_special_remote_for_rclone.mdwn new file mode 100644 index 0000000000..5ec948db41 --- /dev/null +++ b/doc/forum/New_external_special_remote_for_rclone.mdwn @@ -0,0 +1,7 @@ +Hi folks, I'm working on a new external special remote for rclone named "git-annex-remote-rclone-goyle", or "garrgoyle" for short. (I chose a unique name to disambiguate from the preexisting [git-annex-remote-rclone](https://github.com/git-annex-remote-rclone/git-annex-remote-rclone) project.) + +Like git-annex-remote-rclone, garrgoyle only supports the [external special remote protocol](https://git-annex.branchable.com/design/external_special_remote_protocol/). In the near future, I'd like to add support for the *simple export interface* (see [export_and_import_appendix](https://git-annex.branchable.com/design/external_special_remote_protocol/export_and_import_appendix/)). + +Garrgoyle seems to be faster than git-annex-remote-rclone. Anecdotally, it was 10x faster when I asked to copy ~20 files that were already present on a "drive" remote. I think the difference is that garrgoyle pays the rclone startup cost once, rather than once per action. + +I've uploaded a PR to rclone's GitHub repo . If anyone is willing to alpha test, I would greatly appreciate it! Feedback on the PR is also welcome. diff --git a/doc/forum/Possible_to_restore_from_an_encrypted_s3_remote__63__.mdwn b/doc/forum/Possible_to_restore_from_an_encrypted_s3_remote__63__.mdwn new file mode 100644 index 0000000000..6502a5ad5d --- /dev/null +++ b/doc/forum/Possible_to_restore_from_an_encrypted_s3_remote__63__.mdwn @@ -0,0 +1,5 @@ +I tried creating a new git annex repo on my desktop and adding the remote but I think I got an error about both repos not having the same idea. I might be wrong. + +Is it possible to init a git annex repo on my desktop using an encrypted s3 remote? + +thanks