I face with this error in GrAds.The I/O for this variable will be extremely slow because the chunks are too big to fit in the cache .

Question

0.00/5 (No votes)

See more:

Hello,
I face with this error in GrAds in my linux.I dont know what can I do?
could you please help me.
Thank you

*** WARNING! ***
*** The I/O for this variable will be extremely slow
*** because the chunks are too big to fit in the cache
*** chunk size = 12600 bytes (25 * 21 * 6 * 1 * 4 bytes)
*** cache size = 0 bytes
*** There are two ways to control the cache size:
*** add a CACHESIZE entry to the descriptor file
*** or change the cache size scale factor with 'set cachesf'
*** Please read http://iges.org/grads/gadoc/compression.html

Posted 2-Dec-14 23:33pm

Member 11282591

Add a Solution

Comments

Richard MacCutchan 3-Dec-14 6:39am

The messages above explain the issue, and make some suggestions to correct it. What more do you need?

Member 11282591 3-Dec-14 6:44am

thanks for answering.I want to open nc file in grads but I can't and give this error to me.

Richard MacCutchan 3-Dec-14 6:53am

Then please follow the suggestions in the error message.

Member 11282591 3-Dec-14 7:07am

ok, thanks.
I dont know what chunk is.

Richard MacCutchan 3-Dec-14 7:19am

Then you will have to go to the web page in the above link and read the documentation.

Member 11282591 3-Dec-14 7:28am

ok, I try it.
thanks for giving your time to me.

Member 11282591 7-Dec-14 7:21am

hi Mr. Richard MacCutchan
my problem was solved.
Thank you for helping.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)