7 ms·

And that actually works great. We use .Net with postgresql, and lately we have been testing with mono and the results are amazing. Mono + Postgresql is a great

And that actually works great. We use .Net with postgresql, and lately we have been testing with mono and the results are amazing. Mono + Postgresql is a great combination.

sz4kerto 13y ago
Except that the MS CLR is way faster than the Mono CLR (especially under 'weird' loads like what a financial institution might face...)
- skrebbel 13y ago
  Mono gets quite fast if you flip some command-line switches. The defaults are a middle-ground between fast startup time and fast execution. If you're a webapp, you probably don't care about startup time (this is off the top of my head, i forgot where i saw the stats)
  - lneves 13y ago
    Can you give us some detail on what are those command-line switches?
- _random_ 13y ago
  You of course checked the latest version of Mono?
  - sz4kerto 13y ago
    No, I haven't. I mentioned somewhere else that I know of the versions from 2-3 ago. I did _very_ extensive benchmarking, and they were quite far away in edge conditions (example: very high GC load).
- aespinoza 13y ago
  I'm still testing big loads with mono. Once I figure out all the performance bottlenecks, I'll write a blog post about it.
friism 13y ago
Are you getting good performance? Mono is at the bottom of most of the framework comparison benchmarks: http://www.techempower.com/benchmarks/ http://www.techempower.com/benchmarks/
frogcoder 13y ago
Do you use Entity Framework with LINQ? How does that work out for you?
- aespinoza 13y ago
  I actually use Spring.Net + NHibernate... I do use LINQ accross the board, but for NHibernate I am using the Criteria based queries. I am having some problems with Spring.net transactions for NHibernate, but everything else is working great.
  - frogcoder 13y ago
    Thanks, we are considering using mono to move away from windows platform. Won't be using .net tech in the long term. Would be nice to run our existing programs (linq to entity) with just little modifications though.
    - aespinoza 13y ago
      Do consider using Mono. So far it has been a pleasurable experience porting my apps. And C# is way cleaner than Java IMHO.

And that actually works great. We use .Net with postgresql, and lately we have been testing with mono and the results are amazing. Mono + Postgresql is a great combination.

sz4kerto 13y ago

Except that the MS CLR is way faster than the Mono CLR (especially under 'weird' loads like what a financial institution might face...)

skrebbel 13y ago
Mono gets quite fast if you flip some command-line switches. The defaults are a middle-ground between fast startup time and fast execution. If you're a webapp, you probably don't care about startup time (this is off the top of my head, i forgot where i saw the stats)
- lneves 13y ago
  Can you give us some detail on what are those command-line switches?
_random_ 13y ago
You of course checked the latest version of Mono?
- sz4kerto 13y ago
  No, I haven't. I mentioned somewhere else that I know of the versions from 2-3 ago. I did _very_ extensive benchmarking, and they were quite far away in edge conditions (example: very high GC load).
aespinoza 13y ago
I'm still testing big loads with mono. Once I figure out all the performance bottlenecks, I'll write a blog post about it.

friism 13y ago

Are you getting good performance? Mono is at the bottom of most of the framework comparison benchmarks: http://www.techempower.com/benchmarks/ http://www.techempower.com/benchmarks/

frogcoder 13y ago

Do you use Entity Framework with LINQ? How does that work out for you?

aespinoza 13y ago
I actually use Spring.Net + NHibernate... I do use LINQ accross the board, but for NHibernate I am using the Criteria based queries. I am having some problems with Spring.net transactions for NHibernate, but everything else is working great.
- frogcoder 13y ago
  Thanks, we are considering using mono to move away from windows platform. Won't be using .net tech in the long term. Would be nice to run our existing programs (linq to entity) with just little modifications though.
  - aespinoza 13y ago
    Do consider using Mono. So far it has been a pleasurable experience porting my apps. And C# is way cleaner than Java IMHO.