-
Glad to see that you like my work — I really appreciate it!
However, it is not recommended to place OneDev project files on an s3fs mount. OneDev needs to access project files very frequently, and the latency introduced by s3fs will lead to noticeable performance issues, especially for Git operations and repository browsing.
| Type |
Question
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
Issue Votes (0)
Hi there,
Let me start by saying onedev is incredible and the best option out there! I'm really glad to work with it and I'm totally fine if what I'm asking is not doable and that I should follow another approach.
I'm deploying onedev through docker swarm and moved its files to an s3 drive so that the container can be started from any nodes. here is the fstab entry (if that matters) s3fs# /mnt/s3 fuse _netdev,allow_other,use_path_request_style,url=<hetzner_object_storage_url>,use_cache=/tmp/s3fs,multipart_size=100,parallel_count=8,big_writes,kernel_cache,umask=0022,enable_noobj_cache,retries=5,connect_timeout=180,max_dirty_data=1024,passwd_file=<path_to_password_file> 0 0
note that anything between < and > is something I replaced to avoid leaking information. Let me know if I went too far 😇
What I see is that onedev runs quite normally except for anything related to git. I mean by that the screens in onedev for the files or commits and so on. But as well when we do a git pull or git push. The goal was both to be able to have onedev run on different nodes of the swarm as well as having enough space for all our git projects.
Is there something I should do to have better performance with s3 drive or is there no way around with this technology? Is there something else I should put in place for my environment ?
Thank you in advance for your time and the product of such great quality!!
BR, Raphaël.