Yeah, and I guess ioquake3 isn't exactly pushing the boundaries of a single thread on any architecture that will have multiple cores.
- ej On Fri, Jan 21, 2011 at 9:58 PM, Thilo Schulz <[email protected]> wrote: > On Saturday, 22. January 2011 04:43:37 eviljoel wrote: >> Are you saying this to avoid complex programming > > Precisely. > >> I believe contemporary thinking is to split each >> tick into as many threads as possible. > > Maybe for highly parallel applications with huge throughput of data, like > movie encoding. This here is not the application for it. > > -- > Thilo Schulz > > _______________________________________________ > ioquake3 mailing list > [email protected] > http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org > By sending this message I agree to love ioquake3 and libsdl. > _______________________________________________ ioquake3 mailing list [email protected] http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org By sending this message I agree to love ioquake3 and libsdl.
