Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini memberikan informasi pemecahan masalah untuk membantu mengatasi masalah performa yang lambat yang mungkin Anda alami saat menggunakan Filestore.
Pastikan VM klien berada di region yang sama dengan instance Filestore. Pemasangan di seluruh region tidak hanya mengurangi performa, tetapi juga menimbulkan biaya jaringan.
Pastikan instance Filestore Anda tidak berada di atau mendekati kapasitas penuh. Jika kapasitas hampir penuh, ruang yang tersisa akan sangat
terfragmentasi, sehingga menyebabkan operasi baca dan tulis melambat. Jumlah
ruang kosong yang diperlukan untuk menghindari skenario ini bergantung pada kasus. Sebaiknya
siapkan
notifikasi ruang penyimpanan disk hampir penuh.
Uji performa
instance Filestore Anda menggunakan alat fio.
Jika hasil pengujian menunjukkan performa yang lambat secara tidak normal, hubungi perwakilan akun Anda. Jika hasil pengujian menunjukkan performa yang serupa atau lebih besar dari
yang diharapkan, lanjutkan ke bagian berikutnya.
Kasus penggunaan yang menyebabkan performa lambat
Berikut beberapa kasus penggunaan dan skenario yang menyebabkan performa buruk:
Workload yang melibatkan file kecil dalam jumlah besar
Berbagi file Filestore menggunakan opsi ekspor sync untuk keamanan data dan kepatuhan protokol NFS. Untuk sebagian besar operasi yang mengubah data, instance Filestore menunggu data di-commit ke penyimpanan
sebelum membalas permintaan dari VM klien. Jika banyak file terlibat
dalam operasi, klien akan membuat serangkaian operasi sinkron yang panjang
dan latensi kumulatif akan bertambah.
Contoh skenario ini adalah saat Anda mengekstrak arsip di berbagi file,
seperti file tar. TAR membuat banyak operasi sinkron secara berurutan saat
mengekstrak arsip yang berisi banyak file. Akibatnya, performa
akan berkurang.
Jika Anda mencoba menyalin banyak file kecil ke berbagi file, coba paralelkan pembuatan file dengan alat seperti Google Cloud CLI:
mkdir -p /mnt/nfs/many_files_rsync/
time gcloud storage rsync many_files /mnt/nfs/many_files_rsync/ --recursive
Setiap file yang disimpan di berbagi file menggunakan satu inode. Jika sistem file
kehabisan inode, Anda tidak akan dapat menyimpan lebih banyak file di berbagi file
meskipun belum mencapai kapasitas maksimum yang dialokasikan. Namun, mencapai
jumlah inode maksimum jarang terjadi dan hanya menjadi masalah jika Anda perlu
menyimpan banyak file kecil.
Menyalin data dari Cloud Storage ke instance Filestore menggunakan gcloud CLI diketahui lambat. Untuk informasi mendetail tentang cara
meningkatkan performa, lihat
Meningkatkan performa di seluruh Google Cloud resource.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-18 UTC."],[[["\u003cp\u003eThis page helps troubleshoot slow performance issues with Filestore, providing actionable steps to diagnose and resolve them.\u003c/p\u003e\n"],["\u003cp\u003eSlow performance can often be attributed to client VM configuration, such as incorrect machine type, mount options (avoid using \u003ccode\u003esync\u003c/code\u003e), or being in a different region than the Filestore instance.\u003c/p\u003e\n"],["\u003cp\u003eFilestore performance can degrade when the instance is near full capacity, leading to fragmentation and slower read/write operations, so monitoring is crucial.\u003c/p\u003e\n"],["\u003cp\u003eWorkloads involving a high volume of small files can result in slow performance due to the synchronous nature of Filestore operations, and copying data between Cloud Storage and Filestore using the gcloud CLI can be slow as well.\u003c/p\u003e\n"],["\u003cp\u003eTesting performance using \u003ccode\u003efio\u003c/code\u003e is recommended to identify issues, and if performance is slower than expected, contacting an account representative is advised.\u003c/p\u003e\n"]]],[],null,["# Troubleshoot slow performance\n\nThis page provides troubleshooting information to help address slow performance\nissues you might encounter while using Filestore.\n\nSlow read or write performance\n------------------------------\n\n1. Ensure that you are using the\n [recommended machine type](/filestore/docs/performance#client-machine)\n for the client VM.\n\n2. If your client VM is running Linux, confirm that you're using the\n [default mount options](/filestore/docs/performance#linux_client_mount_options).\n\n | **Note:** Using the `sync` client mount option significantly reduces performance.\n3. Ensure that the client VM is located in the same region as the\n Filestore instance. Mounting across regions not only reduces\n performance, it also incurs a [networking cost](/vpc/network-pricing).\n\n4. Ensure that your Filestore instance isn't at or near full\n capacity. When capacity is nearly full, any remaining space is highly\n fragmented, causing read and write operations to slow down. The amount of\n free space needed to avoid this scenario is case-dependent. We recommend\n setting up\n [low disk space alerts](/filestore/docs/monitoring-instances#low-disk-space).\n\n For more information, see [Troubleshoot capacity issues](/filestore/docs/capacity-issues).\n5. [Test the performance](/filestore/docs/performance#testing_performance)\n of your Filestore instance using the `fio` tool.\n\n If the test results show abnormally slow performance, contact your account\n representative. If the test results show similar or greater performance than\n expected, continue to the next section.\n\nUse cases that cause slow performance\n-------------------------------------\n\nHere are some use cases and scenarios that cause poor performance:\n\n### Workloads involving high volumes of small files\n\n- Filestore file shares use the `sync` export option for data safety\n and NFS protocol compliance. For most data-modifying operations, the\n Filestore instance waits for the data to be committed to storage\n before replying to requests from the client VM. When many files are involved\n in an operation, the client makes a long series of synchronous operations\n and the cumulative latency adds up.\n\n An example of this scenario is when you extract an archive on the file share,\n like tar files. TAR makes many synchronous operations in a series when\n extracting an archive containing many files. As a result, performance is\n reduced.\n\n If you're trying to copy many small files to a file share, try parallelizing\n file creation with a tool like the [Google Cloud CLI](/sdk/gcloud/reference/storage/rsync): \n\n mkdir -p /mnt/nfs/many_files_rsync/\n time gcloud storage rsync many_files /mnt/nfs/many_files_rsync/ --recursive\n\n- Each file stored on the file share consumes one inode. If the file system\n runs out of inodes, you won't be able to store more files on the file share\n even if you haven't reached the maximum allocated capacity. However, reaching\n the maximum number of inodes is rare and is only a concern if you need to\n store numerous small files.\n\n For more information, see [Inode usage](/filestore/docs/scale#inode-usage).\n\n### Copying data between Cloud Storage and Filestore\n\nCopying data from Cloud Storage to a Filestore instance using the\ngcloud CLI is known to be slow. For detailed information on how to\nimprove performance, see\n[Improve performance across Google Cloud resources](/filestore/docs/performance#across-resources).\n\nWhat's next\n-----------\n\n- [Troubleshoot capacity issues](/filestore/docs/capacity-issues)\n- [Improve performance across Google Cloud resources](/filestore/docs/performance#across-resources).\n- [Scale capacity](/filestore/docs/scale)."]]
