• next question.

    From Chris Hoppman@1:129/305 to All on Mon Dec 15 20:56:32 2003
    Which is faster..

    type
    UsersRec = record
    FirstName : String[35];
    LastName : Stirng[35];
    Alias : String[60];
    Password : String[12];
    end;{record usersrec}

    Var
    Users : File of UsersRec;
    Users : UsersRec;
    begin
    {etc etc}

    end.

    Or the same, but using pointers.

    chris

    --- Renegade v12-15.3 - Alpha
    * Origin: The Titantic BBS Telnet - ttb.slyip.com (1:129/305)
  • From mark lewis@1:3634/12 to Chris Hoppman on Mon Dec 15 23:35:42 2003
    Which is faster..

    type
    UsersRec = record
    FirstName : String[35];
    LastName : Stirng[35];
    Alias : String[60];
    Password : String[12];
    end;{record usersrec}

    Var
    Users : File of UsersRec;
    Users : UsersRec;
    begin
    {etc etc}

    end.

    Or the same, but using pointers.

    dunno that speed is really a factor... the type of memory used is different, though...

    )\/(ark


    * Origin: (1:3634/12)
  • From Scott Adams@1:112/91 to Chris Hoppman on Wed Dec 17 00:24:17 2003
    Quoting Chris Hoppman to All <=-


    type
    UsersRec = record
    FirstName : String[35];
    LastName : Stirng[35];
    Alias : String[60];
    Password : String[12];
    end;{record usersrec}

    Var
    Users : File of UsersRec;
    Users : UsersRec;
    begin
    {etc etc}

    In modern machines with gighz machines and such it
    really isn't that much unless your doing a data hog
    like a Database program. But a rule of thumb basically
    anything is better with pointers. The main benefit is
    data storage of course but speed helps.
    So it depends on how many records you might be dealing with.
    A few hundred who cares. A million then yeah use pointers. :)




    ... Coffee - 2 sugars - cream - and aspirin.
    --- Fringe BBS
    * Origin: EWOG II - The Fringe - 904-733-1721 (1:112/91)
  • From Chris Hoppman@1:129/305 to Mark Lewis on Tue Dec 16 10:28:57 2003
    dunno that speed is really a factor... the type of memory used is different though...

    hrm, my program is real mode only. I don't think I can get it to use dmpi,
    but can use xms,ems,or disk.

    Talk to me like a 11 year old that is learning this for the first time, because I am learning this for the first time and need someone to talk that slow and explain everything to me. I know alot, but when it comes to using real mode vs protectted dmpi mode, heap, stack, xms, ems, disk. I need just that. (btw i am 25.. I just said 11 cause i would explain things more slowly to a 11 yr old)

    chris

    --- Renegade v12-15.3 - Alpha
    * Origin: The Titantic BBS Telnet - ttb.slyip.com (1:129/305)
  • From Jasen Betts@3:640/1042 to Chris Hoppman on Wed Dec 17 06:23:37 2003
    Hi Chris.

    15-Dec-03 20:56:32, Chris Hoppman wrote to All


    Which is faster..

    [code snipped]

    it will take zero time to execute because there is no computation done.

    Or the same, but using pointers.

    see above.

    Bye <=-

    ---
    * Origin: You think "I'm no fool!" but I am! - Spike Milligan (3:640/1042)
  • From mark lewis@1:3634/12 to Chris Hoppman on Thu Dec 18 01:14:34 2003
    dunno that speed is really a factor... the type of memory
    used is different though...

    hrm, my program is real mode only. I don't think I can
    get it to use dmpi, but can use xms,ems,or disk.

    sorry, i was thinking about stack or heap memory...

    Talk to me like a 11 year old that is learning this for
    the first time, because I am learning this for the first
    time and need someone to talk that slow and explain
    everything to me. I know alot, but when it comes to
    using real mode vs protectted dmpi mode, heap, stack,
    xms, ems, disk. I need just that. (btw i am 25.. I just
    said 11 cause i would explain things more slowly to a 11
    yr old)

    all the coding i've done, even now, today, is plain old DOS 5 type coding versus 32bit flat memory model coding where 128Meg of RAM is all accessible if one wants it... everything i do is still the old fashioned xms and ems swapping
    type stuff...

    )\/(ark


    * Origin: (1:3634/12)
  • From Chris Hoppman@1:129/305 to Scott Adams on Thu Dec 18 13:57:43 2003
    In modern machines with gighz machines and such it
    really isn't that much unless your doing a data hog
    like a Database program. But a rule of thumb basically
    anything is better with pointers. The main benefit is
    data storage of course but speed helps.
    So it depends on how many records you might be dealing with.
    A few hundred who cares. A million then yeah use pointers. :)

    How, about 2-10 records at a time. The program is okay when one user is on the bbs, but when a second or third user is on the bbs then it is all hell tring to type something in the telnet client. The keys seem like they stick. (Wait a few seconds, before they get printted to the screen).

    The ansi screens scrolls about 3 lines then pauses then scrolls two more then pauses then scrolls 5 more (not in that order, but in general it does that). When two users are online. It sucks and I am looking to resolve the issue of cpu usage then maybe speed up the program.

    chris

    --- Renegade v12-15.3 - Alpha
    * Origin: The Titantic BBS Telnet - ttb.slyip.com (1:129/305)
  • From Scott Adams@1:112/91 to Chris Hoppman on Mon Jan 12 00:16:41 2004
    Quoting Chris Hoppman to Scott Adams <=-

    In modern machines with gighz machines and such it
    really isn't that much unless your doing a data hog
    like a Database program. But a rule of thumb basically
    anything is better with pointers. The main benefit is
    data storage of course but speed helps.
    So it depends on how many records you might be dealing with.
    A few hundred who cares. A million then yeah use pointers. :)

    How, about 2-10 records at a time. The program is okay when one user
    is on the bbs, but when a second or third user is on the bbs then it
    is all hell tring to type something in the telnet client. The keys
    seem like they stick. (Wait a few seconds, before they get printted to
    the screen).

    IF only 2-10 then nah pointers not mandatory. But if your running
    say a million records and USE 2-10 at a time then reding with
    pointers might help.

    The ansi screens scrolls about 3 lines then pauses then scrolls two
    more then pauses then scrolls 5 more (not in that order, but in
    general it does that). When two users are online. It sucks and I am looking to resolve the issue of cpu usage then maybe speed up the program.

    OH ...I see...a multi-user board yes definitely needs timeslices.





    ... Sinclair - "Your `noble citizens' have stolen credit chips."
    --- Fringe BBS
    * Origin: EWOG II - The Fringe - 904-733-1721 (1:112/91)