Thread: Differing performance between exec in terminal and terminal in KATE

  1. #1
    Registered User
    Join Date
    Apr 2010
    Posts
    88

    Differing performance between exec in terminal and terminal in KATE

    Hi. I wrote a version of Reynolds' flocking boids as a first foray into openGL. I'm happy with the algorithm and it looks as one would visually expect, but I am wondering about one thing:

    When I compile and run the program from the terminal built into KATE (a text editor), the code and graphics perform very quickly, at a highly interactive rate.

    However, when I run the same program from a the very same source files in a normal Scientific Linux terminal, there is visually slower performance (a clear lag between frames). Any ideas what could be causing this?

    Ocifer
    W7, Ubuntu -- mingw, gcc, g++, code::blocks, emacs, notepad++

  2. #2
    ATH0 quzah's Avatar
    Join Date
    Oct 2001
    Posts
    14,826
    Different hardware?


    Quzah.
    Hope is the first step on the road to disappointment.

  3. #3
    Registered User
    Join Date
    Apr 2010
    Posts
    88
    Sorry, I should have mentioned that this was all on the same machine, using the same operating system (Scientific Linux 6).

    KATE provides a terminal within the program itself and I'm finding that when I execute the program in the terminal within KATE, the program runs noticeably faster than when I use the normal Linux terminal. It doesn't seem to matter where/how I compile it, only where I'm executing seems to make a difference.
    W7, Ubuntu -- mingw, gcc, g++, code::blocks, emacs, notepad++

  4. #4
    Registered User
    Join Date
    Oct 2006
    Posts
    250
    Are you by any chance using GLUT?
    iMalc: Your compiler doesn't accept misspellings and bad syntax, so why should we?
    justin777: I have no idea what you are talking about sorry, I use a laptop and there is no ascii eject or something

  5. #5
    Registered User
    Join Date
    Apr 2010
    Posts
    88
    Yes, I am using some glut functions to set up the display window.
    W7, Ubuntu -- mingw, gcc, g++, code::blocks, emacs, notepad++

  6. #6
    Registered User
    Join Date
    Oct 2006
    Posts
    250
    I had a similar issue a long time ago, never figured out the underlying cause. SDL is about as easy to setup as GLUT and solved the problem for me at the time.
    iMalc: Your compiler doesn't accept misspellings and bad syntax, so why should we?
    justin777: I have no idea what you are talking about sorry, I use a laptop and there is no ascii eject or something

  7. #7
    Registered User
    Join Date
    Apr 2010
    Posts
    88
    Thanks, I'll look into SDL, I was going to take a look anyway.
    W7, Ubuntu -- mingw, gcc, g++, code::blocks, emacs, notepad++

  8. #8
    Registered User
    Join Date
    Apr 2010
    Posts
    88
    Good call, MWAAAHAAA, upon delegating the windowing to SDL functions, the performance is quick in all terminals. I like SDL, it's not too difficult to learn. Now I have to look up some optimization for the spatial sorting of the Boids, I want to do huge swarms. It's currently doing n^2 comparisons each frame around, so as n goes above 100 you really start to notice it in the framerate on my laptop.
    W7, Ubuntu -- mingw, gcc, g++, code::blocks, emacs, notepad++

Popular pages Recent additions subscribe to a feed

Similar Threads

  1. Terminal-run
    By Muscovy in forum Linux Programming
    Replies: 23
    Last Post: 06-20-2009, 09:53 PM
  2. Console, Terminal and Terminal Emulator
    By lehe in forum C Programming
    Replies: 4
    Last Post: 02-15-2009, 09:59 PM
  3. GCC with MAC Terminal
    By dcwang3 in forum Linux Programming
    Replies: 8
    Last Post: 08-28-2008, 01:05 PM
  4. using su with pseudo terminal
    By oncemyway in forum Linux Programming
    Replies: 2
    Last Post: 04-30-2007, 10:52 AM
  5. Terminal Warning gets()
    By macman in forum C++ Programming
    Replies: 6
    Last Post: 04-09-2005, 11:57 AM