IsNotNull
Help with concurrency blocking issue
@mtreit I agree, I just meant that the pauses increase in relative expense with the number of active threads you have. There is some threshold (in allocation rate and active threads) where it costs less to split the work across processes...and I bet its a lower threshold than we would want to know about; probably at a level that most of us would claim its a premature optimization or too annoying/complicated to support in a hand-waivey way.
26 replies
Help with concurrency blocking issue
The 'fundamentals' GC page mentions this offhand. I bet on CPU bound and allocation heavy code, that the threshold before its worth partitioning data to IPC to child processes to handle is probably a lot lower than most devs expect (assuming the inputs and outputs are reasonable to serialize).
26 replies
Help with concurrency blocking issue
The GC docs feel a bit inconsistent. They have contemporary verbiage indicating some features have replaced others and then out-of band warnings claiming some things don't apply if you are using NET FX. Its really hard to tell what applies in a bog standard .NET 5.0+ project by default
26 replies
ASP.NET error when pulling data from Db???
The obj folder contains files visual studio is working with as it has the project open. It copies those to bin when it does a build or before debugging. If you are running your project from the bin folder (for exapmle, you ran 'dotnet run') when VS tries to do a build, it can get this error. This can also happen if the last run of your project didn't exit properly, if a virus software has the file locked, or any other reason that causes the file to be locked.
If you have this error in VS, then whatever you think you are running when 'pulling data from the Db' is probably out of date with the code you are editing, as your build(s) are failing.
4 replies
Exception about disposing DbContext
Does 'Guild' have any EF relation properties? You are putting the 'Guild' entry into a memory cache that outlives the DbContext it came from. If you try to access a relation property, it will try to use the disposed context to query the related entity and then throw an error like this.
10 replies