Page 3 of 3
Re: How do I start? For real.
Posted: Mon Aug 10, 2015 4:34 pm
by neon
My goal wasn't to change your mind. My goal was to demonstrate your
willful ignorance. I have done that, so no point in farther discussion. We don't use any hacks by the way, our build environment is rather very clean. I concede quickly that the VS page in the Wiki uses a lot of hacks -- it isn't a good example -- which is why I offered to provide a sample of what we do instead. Many of us on the forums use VS without any issues
at all. (For the record, it works with
all versions of VS post 2005.) The fact that you simply
do not care to educate yourself on the build process used by those that do use VS and your constant
assumptions and
ad-hoc attacks demonstrates your willful ignorance.
So my work is done here.
I'm sorry you couldn't change my mind, but that's no excuse to insult me and then edit your post three
I tend to edit my posts a bit as needed to make clarifications or add content. I apologize if it caused any confusion. I consider my original insult warranted given your ad hoc attacks and blanket dishonesty as depicted in this thread. The
only reason I decided to remove it was to keep the thread clean. We should also keep on topic -- and given that we are not getting anywhere, there is no point in continuing.
Re: How do I start? For real.
Posted: Tue Aug 11, 2015 2:16 pm
by Octacone
solved
Re: How do I start? For real.
Posted: Tue Aug 11, 2015 5:28 pm
by Brendan
Hi,
thehardcoreOS wrote:I've just installed Linux Mint, it is epic. It is 100 times better for OSDeving than Windows. The only problem I got right now it that sometimes it is unresponsive. It laggs a bit (1GB ram, can't add more, only have 2GB). When I want to click on that exit button it laggs, when I want to drag a window around it laggs, etc... Can if fix that lag by buying 4GB ram stick (upgrading my laptop)?
The problem is that the Linux scheduler is "less good" - it has no task priorities, so less important things (e.g. 50 compiler processes all starting/stopping at "random" times) all get CPU time when there are more important things (e.g. GUI responsiveness) that the OS should be doing instead. Increasing the amount of RAM won't help. However; the problem becomes less noticeable when you have more CPUs because there's more chance of the important task getting scheduled on a CPU sooner; so increasing the number of logical CPUs would help.
thehardcoreOS wrote:Now my question is: can I still make 32bit OS on 64bit Linux/Windows without any problems at all?
You can make a 32-bit OS on 64-bit Linux/Windows, and make a 64-bit OS on 32-bit Linux/Windows, and even make an OS for one CPU while using a different CPU (e.g. create an ARM OS while using 80x86). The only real problem is that you'll need tools (e.g. a compiler) that supports the target architecture and not the current computer's architecture. Depending on which tools you use and how badly they're designed, this can mean "do nothing because it just works" or could mean "you have to build your own cross compiler".
Cheers,
Brendan
Re: How do I start? For real.
Posted: Thu Aug 13, 2015 3:04 am
by Octacone
solved
Re: How do I start? For real.
Posted: Thu Aug 13, 2015 4:01 am
by Kevin
Probably not, and it's highly unlikely that the scheduler has anything to do with it because I assume that you're not running those 50 parallel compiler processes that Brendan mentioned. And even when running massive compile jobs, my GUI is always responsive these days on a native Linux installation (that used to be different ten years ago).
What's more likely is that the guest is swapping (and then more memory would help) or just busy doing fancy graphics with a stupid framebuffer and no hardware support. For both problems, I'd rather consider a native Linux installation without a VM than throwing more hardware at it, but in case it's the latter: Did you make sure to install the VBox guest additions?
Edit: And it seems that you need to manually enable hardware video acceleration in VBox before you can use the guest addition drivers for it; that doesn't seem to be the default.
Re: How do I start? For real.
Posted: Thu Aug 13, 2015 4:39 am
by Brendan
Hi,
Kevin wrote:Probably not, and it's highly unlikely that the scheduler has anything to do with it because I assume that you're not running those 50 parallel compiler processes that Brendan mentioned. And even when running massive compile jobs, my GUI is always responsive these days on a native Linux installation (that used to be different ten years ago).
You don't need 50 parallel compiler processes. For dual core (what I assumed the original poster is using) you only really need a few processes.
My GUI is almost always responsive in Linux (because I'm using 16 CPUs and not 2), where "always" means it's only really noticeable (but still acceptable when it is noticeable) when compiling something large. If you have fewer CPUs than me and can't notice the difference when compiling larger projects, then you've probably failed to use "make -j" (or have a habit of going to get coffee while you wait or something).
Kevin wrote:What's more likely is that the guest is swapping (and then more memory would help) or just busy doing fancy graphics with a stupid framebuffer and no hardware support. For both problems, I'd rather consider a native Linux installation without a VM than throwing more hardware at it, but in case it's the latter: Did you make sure to install the VBox guest additions?
That's also possible. I assumed the original poster was using real hardware and not a VM, and would've heard the hard drive trashing due to swapping if that was the case.
Cheers,
Brendan
Re: How do I start? For real.
Posted: Thu Aug 13, 2015 6:39 am
by Kevin
Brendan wrote:My GUI is almost always responsive in Linux (because I'm using 16 CPUs and not 2), where "always" means it's only really noticeable (but still acceptable when it is noticeable) when compiling something large. If you have fewer CPUs than me and can't notice the difference when compiling larger projects, then you've probably failed to use "make -j" (or have a habit of going to get coffee while you wait or something).
Okay, I tried it and it is in fact noticable when you pay attention. I started a qemu build (with -j16 on a laptop with 2 cores/4 threads) and dragged a window in circles, and yes, sometimes the window jumps a few pixels, which it doesn't do without the build in the background. Not really bad, and I wouldn't call it "unresponsive", but I can notice it.
Usually I don't drag windows in circles, though, so in practice it doesn't matter much for me and I'd expect that you have something worse when you ask for help in a forum.