Slow performance when using UNICODE_FSS charset
Posted: Wed 11 Apr 2012 09:27
Hello!
I've ran into the following problem:
When dealing with larger resultsets, if the charset is set to UNICODE_FSS the performance of IBDAC slows down drastically.
IE.: 10.000 records are loaded in about 3-4 secs with the UTF8 charset.
With the same settings if charset is set to UNICODE_FSS it takes IBDAC almost 40 seconds to load the same number of records on the same computer.
Initially, I was using UTF8 for connecting in my program. But IBDAC version 3.50.0.19 released 08-Dec-10 introduced the following fix:
"Now the UTF8 charset is used instead of UNICODE_FSS, when TIBCConnectionOptions.UseUnicode is True and Charset is set to 'UTF8'"
Since then, without setting the charset to UNICODE_FSS I was experiencing various problems in my program.
My question is: is this a bug in IBDAC and is there a workaround without setting the charset to UTF8?
Thanks!
I've ran into the following problem:
When dealing with larger resultsets, if the charset is set to UNICODE_FSS the performance of IBDAC slows down drastically.
IE.: 10.000 records are loaded in about 3-4 secs with the UTF8 charset.
With the same settings if charset is set to UNICODE_FSS it takes IBDAC almost 40 seconds to load the same number of records on the same computer.
Initially, I was using UTF8 for connecting in my program. But IBDAC version 3.50.0.19 released 08-Dec-10 introduced the following fix:
"Now the UTF8 charset is used instead of UNICODE_FSS, when TIBCConnectionOptions.UseUnicode is True and Charset is set to 'UTF8'"
Since then, without setting the charset to UNICODE_FSS I was experiencing various problems in my program.
My question is: is this a bug in IBDAC and is there a workaround without setting the charset to UTF8?
Thanks!