digitalmars.D.announce - Mono-D v0.4.9.9 Bug fixes
- alex (26/26) Feb 10 2013 Hi everyone,
- F i L (7/7) Feb 10 2013 Yeah it takes probably 20-40 seconds on my Phenom II X4 920 (Arch
- alex (4/11) Feb 10 2013 I've got to step deeper into this, I guess. Parsing phobos &
- Johannes Pfau (3/15) Feb 11 2013 ~20 seconds here on fedora 17 with ufcs.
- Tobias Pfaff (8/26) Feb 11 2013 ~6 seconds on Windows, never really was a problem.
- alex (4/27) Feb 11 2013 I just found out: It's not the parser, it's probably a deadlock -
Hi everyone, Just released another bunch of bug fixes & solved issues http://mono-d.alexanderbothe.com/?p=840 May I ask you how long you have to wait for phobos stuff to pop up in the completion list after you launched Mono-D? I've just installed a non-virtual Mint and had to experience wait very long until stuff like std showed up.. but here on my Windows machine, it just takes ~3 seconds to parse everything + UFCS preparation, so at least as half as long as it takes on the Linux installation..wth? I've compiled all the stuff manually to check where some fundamental reasons are located for this - it ran faster (but still not fast enough) after I disabled multi-threading! Whereas on Windows, I actually established a multi-threaded environment for all the analysis tasks!? -- Mad stuff. What's really interesting is that it takes about 170-200 ms to parse std.datetime on both platforms - so not really different at all. Again, mad stuff. Anyway I've always thought everything would be fine with the analysis performance - even on my small Netbook rig from 2011 that is driven by a tiny 1.66 GHz Atom CPU with Win7 on it only takes 5 seconds for everything - even less than Mono takes for parsing phobos with 2(!) threads.. Still troubleshooting so far.. Oh, and please keep reporting issues - just raging silently and immediately uninstalling the addin isn't making it better at all! https://github.com/aBothe/Mono-D/issues
Feb 10 2013
Yeah it takes probably 20-40 seconds on my Phenom II X4 920 (Arch Linux 64). Haven't MonoD on Windows (or Mac) in awhile, so I haven't noticed any difference. I think MonoDevelop on Windows actually uses MS .NET (not Mono).. could be wrong about that, but if it's true, that could be the reason for the slow down (Mono is much slower than MS .Net). Thanks for the update!
Feb 10 2013
"alex" <info alexanderbothe.com> On Monday, 11 February 2013 at 03:18:41 UTC, F i L wrote:Yeah it takes probably 20-40 seconds on my Phenom II X4 920 (Arch Linux 64). Haven't MonoD on Windows (or Mac) in awhile, so I haven't noticed any difference. I think MonoDevelop on Windows actually uses MS .NET (not Mono).. could be wrong about that, but if it's true, that could be the reason for the slow down (Mono is much slower than MS .Net). Thanks for the update!I've got to step deeper into this, I guess. Parsing phobos & druntime & ufcs args in MonoDevelop took 1.8 seconds, a last test in D-IDE resulted in 1.7 seconds..awkwardly strange!
Feb 10 2013
Am Mon, 11 Feb 2013 03:25:25 +0100 schrieb "alex" <info alexanderbothe.com>:Hi everyone, Just released another bunch of bug fixes & solved issues http://mono-d.alexanderbothe.com/?p=840 May I ask you how long you have to wait for phobos stuff to pop up in the completion list after you launched Mono-D? I've just installed a non-virtual Mint and had to experience wait very long until stuff like std showed up.. but here on my Windows machine, it just takes ~3 seconds to parse everything + UFCS preparation, so at least as half as long as it takes on the Linux installation..wth?~20 seconds here on fedora 17 with ufcs.
Feb 11 2013
On Monday, 11 February 2013 at 09:07:59 UTC, Johannes Pfau wrote:Am Mon, 11 Feb 2013 03:25:25 +0100 schrieb "alex" <info alexanderbothe.com>:~6 seconds on Windows, never really was a problem. For some reason, though, the completion of my own types and local variables is really flaky. Sometimes it doesn't work for hours (with code that mostly compiles), so Monodevelop constantly tries to replace my methods with weird Phobos UFCS functions, and then completion suddenly comes back. I haven't figured out yet what triggers it -- if I do, I'll file a bug report.Hi everyone, Just released another bunch of bug fixes & solved issues http://mono-d.alexanderbothe.com/?p=840 May I ask you how long you have to wait for phobos stuff to pop up in the completion list after you launched Mono-D? I've just installed a non-virtual Mint and had to experience wait very long until stuff like std showed up.. but here on my Windows machine, it just takes ~3 seconds to parse everything + UFCS preparation, so at least as half as long as it takes on the Linux installation..wth?~20 seconds here on fedora 17 with ufcs.
Feb 11 2013
On Monday, 11 February 2013 at 09:07:59 UTC, Johannes Pfau wrote:I just found out: It's not the parser, it's probably a deadlock - though I don't know why it's actually working under .Net then.. But okay, I've got a trace, I'll try to fix it - and I've got a 0.5 version then.Am Mon, 11 Feb 2013 03:25:25 +0100 schrieb "alex" <info alexanderbothe.com>:Hi everyone, Just released another bunch of bug fixes & solved issues http://mono-d.alexanderbothe.com/?p=840 May I ask you how long you have to wait for phobos stuff to pop up in the completion list after you launched Mono-D? I've just installed a non-virtual Mint and had to experience wait very long until stuff like std showed up.. but here on my Windows machine, it just takes ~3 seconds to parse everything + UFCS preparation, so at least as half as long as it takes on the Linux installation..wth?~20 seconds here on fedora 17 with ufcs.
Feb 11 2013