Closer look revealed the problem was not in QuickFix.
Our code was using ThreadLocal<T> to reference the QuickFix42.NewOrderSingle
object. For some reason, the transition from .NET 3.5 to .NET 4.0 has
dramatically slowed down referencing a
ThreadLocal<QuickFix42.NewOrderSingle> . When this was changed to a regular
instance variable, the performance problems disappeared.
If you have any thoughts on why this is happened, I'm sure the forum will
appreciate hearing from you!
sevzas wrote:
>
> We've been using quickfix 1.13.3 built using VS 2008 targeting X64 for a
> little over a year.
>
> During the process of upgrading our .NET app to use Visual Studio 2010 /
> .NET 4.0, I rebuilt QuickFix using VS 2010.
>
> I find that while nearly all of my app has registered significant
> performance gains under .NET 4.0, the Quickfix functionality is about
> *half* as fast - twice as slow.
>
> I determined this using Eqatec 3.3 profiler. Regular "user" testing
> confirms this. Unfortunately Eqatec will not allow me to profile mixed
> mode assemblies, so I cannot profile inside QuickFix. Before I bring in
> another profiling tool, I wanted to reach out to the Quickfix user
> community to see if anyone has experienced this.
>
> I see the slowness with both the Release and the Debug builds.
>
>
--
View this message in context: http://old.nabble.com/QuickFix-1.13.3-much-slower-after-upgrade-to-Visual-Studio-2010---.NET-4.0-tp31481080p31534825.html
Sent from the QuickFIX - User mailing list archive at Nabble.com.
|
