Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.

Note: this post will not display until it's been approved by a moderator.

Name:
Email:
Subject:
Message icon:
Verification:
This site name www.[site].com?:

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: Admin
« on: April 20, 2011, 20:28:04 »

Could you, please, send us your logs for detailed analysis.
Posted by: Springdream
« on: April 17, 2011, 11:01:22 »

Memory is 2GB, Files approx 120.000
If it is a memory problem, shoulds similarity tell me?
Posted by: Admin
« on: April 17, 2011, 10:59:08 »

Quote from: Springdream on April 10, 2011, 15:22:36
Sometimes I get far to many results (e.g. 10000 files with 300000 results for identical files).
It looks likes that for a certain time period file comparison with "precise" returns very quickly 100% instead of really comparing the files.
Maybe it is related to CUDA?
How much RAM memory do you have ? And how much files do you scan ?
This issue related to "no memory" problem.
Posted by: Springdream
« on: April 17, 2011, 10:53:05 »

in the log I get:
CIppsVector::insert:244 failed [false]
quite often
maybe it is related to it?
Posted by: Springdream
« on: April 11, 2011, 16:16:11 »

well I was using a MSI card with Nvidia GTX460, the same card that was used for your tutorial...
I get no error and Benchmark is fine...
Also an indicator for developers: the result returns much faster than the normal calculation result...
Posted by: Admin
« on: April 11, 2011, 12:44:57 »

Yes, in beta version please use "benchmark" button to check correct calculation, we add warning before enabling OpenCL without checking.
And use latest beta version we corrected behaviour with old/low-end ATI videocards.
Posted by: hsei
« on: April 10, 2011, 19:39:38 »

When you enabled OpenCL in the corresponding options tap you better start a benchmark run first. I got an "calculation error" (AMD/ATI 5570) and most comparison results gave false 100% indication.
Only way out in this case: Switch off OpenCL (CUDA).
Posted by: Springdream
« on: April 10, 2011, 15:22:36 »

Sometimes I get far to many results (e.g. 10000 files with 300000 results for identical files).
It looks likes that for a certain time period file comparison with "precise" returns very quickly 100% instead of really comparing the files.
Maybe it is related to CUDA?