You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm conducting these tests on an r6id.8xlarge EC2 instance using AMI ami-0c5cd894db560d66c and both the bucket and the instance are in the same region.
What happened?
While running the Fio benchmarks on your repository, I observed a significant discrepancy between the results of seq_read_direct.fio and seq_read.fio. With direct mode enabled, I achieve a bandwidth of ~1300MB/s; however, without direct mode, the bandwidth drops sharply to ~3MB/s.
Furthermore, simple transfer benchmarks using tools like dd, cp, and cat also yield slower results — much below the expected ~1300MB/s.
To mount the bucket, I'm using the following command:
Is there a potential misstep in my approach? Do I need to specify any additional parameters? Alternatively, could this be a bug related to the absence of direct mode?
Mountpoint for Amazon S3 version
mount-s3 1.0.0
AWS Region
eu-west-1
Describe the running environment
I'm conducting these tests on an
r6id.8xlarge
EC2 instance using AMIami-0c5cd894db560d66c
and both the bucket and the instance are in the same region.What happened?
While running the Fio benchmarks on your repository, I observed a significant discrepancy between the results of
seq_read_direct.fio
andseq_read.fio
. With direct mode enabled, I achieve a bandwidth of ~1300MB/s; however, without direct mode, the bandwidth drops sharply to ~3MB/s.Furthermore, simple transfer benchmarks using tools like
dd
,cp
, andcat
also yield slower results — much below the expected ~1300MB/s.To mount the bucket, I'm using the following command:
Is there a potential misstep in my approach? Do I need to specify any additional parameters? Alternatively, could this be a bug related to the absence of direct mode?
Relevant log output
The text was updated successfully, but these errors were encountered: