Hello. docs.stssoft.com appears to be down today, and I'm not sure where to find this information without that.
What .net libraries does STSdb depend on? Can it run under the dot net core libraries (CoreFX)?
Thanks,
Mark Shirley
Hello. docs.stssoft.com appears to be down today, and I'm not sure where to find this information without that.
What .net libraries does STSdb depend on? Can it run under the dot net core libraries (CoreFX)?
Thanks,
Mark Shirley
Greetings Mark.
It appears that the CoreFX contains all of the needed libraries by STSdb, but the best way to know is to try and run it.
The .NET Portability Report tool indicates several dozen issues when run on STSdb 4.0.9 wrt running under .NET Core,Version=v5.0. The portability tool hasn't been updated all that recently, so it's only an indication.
I'm part way through trying to get it to run under .NET Core RC2, which was just released. Most of the hundreds of errors are easy, but many remain. For instance, I'm currently stuck on the lack of CSharpCodeProvider and AppDomain.
The code contains a conditional compilation symbol of NETFX_CORE, but this wraps very few of the porting issues. Do you know whether there has been any serious effort to port STSdb to .NET Core since I asked earlier?
Thanks,
Mark Shirley
I'm at the same point as you, mshirley. I'm trying to use STSdb in a new project which is written in .net core, but the differences are not that simple. STSdb depends on things like binary serialization or the codedom compiler that has been replaced by roselyn.
I would also like to see a real movement to migrate the old STSdb to .net core.
Thanks,
jimyx17
I finally got it working with .net core in both linux and windows.
The tets I'm running by now are pretty simple but are throwing a solid performance:
.net 4.6:
Inserting...
Inserted 100000 records
Inserted 200000 records
Inserted 300000 records
Inserted 400000 records
Inserted 500000 records
Inserted 600000 records
Inserted 700000 records
Inserted 800000 records
Inserted 900000 records
Inserted 1000000 records
Insert speed:309693,403530505 rec/sec
Reading...
Read 100000 records
Read 200000 records
Read 300000 records
Read 400000 records
Read 500000 records
Read 600000 records
Read 700000 records
Read 800000 records
Read 900000 records
Read 1000000 records
Read speed:513610,683102208 records
.net core "Windows":
Inserting...
Inserted 100000 records
Inserted 200000 records
Inserted 300000 records
Inserted 400000 records
Inserted 500000 records
Inserted 600000 records
Inserted 700000 records
Inserted 800000 records
Inserted 900000 records
Inserted 1000000 records
Insert speed:278629,144608526 rec/sec
Reading...
Read 100000 records
Read 200000 records
Read 300000 records
Read 400000 records
Read 500000 records
Read 600000 records
Read 700000 records
Read 800000 records
Read 900000 records
Read 1000000 records
Read speed:546448,087431694 records
.net core "Linux":
netcoreapp1.0]# dotnet STSdb_core_test.dll
Inserting...
Inserted 100000 records
Inserted 200000 records
Inserted 300000 records
Inserted 400000 records
Inserted 500000 records
Inserted 600000 records
Inserted 700000 records
Inserted 800000 records
Inserted 900000 records
Inserted 1000000 records
Insert speed:284738.041002278 rec/sec
Reading...
Read 100000 records
Read 200000 records
Read 300000 records
Read 400000 records
Read 500000 records
Read 600000 records
Read 700000 records
Read 800000 records
Read 900000 records
Read 1000000 records
Read speed:489236.790606654 records
Even though, I'm not a .net expert so I'm still looking forward for a proffesional port to .net core. I would expect a much higher quality port.
Thanks!
Jimyx17,
It's good to hear you've made progress with .net core. How extensive were the changes you needed to make?
Is there any sense of how active development is? I can't tell. The forums seem pretty dead.
- Mark Shirley
33
mhshirley,
The changes weren't extensive at all, furthermore, the compatibility reporting tool points out most of the issues. The only tricky incompatibility is the one with the appdomain. The rest is just taking care of the api changes, like the serializacion or the getbuffer call from memorystream objects.
That being said, I don't know if it worth the effort because .net core is going to change quite a lot in the following months when the 1.2 version gets released.
About the stsdb current status, its a pitty but github repos are completelly abandones, forums are dead and there havent been any minor or major update in the last year.
In this situación I don't know if this db is a good option for produccion env... What a pity!
Jimyx17