From: Mikael Adlers <mikael@mathcore.com>
To: 'Kai Trukenmueller' <trukenm@ag2.mechanik.tu-darmstadt.de>,
gsl-discuss@sources.redhat.com
Subject: RE: gsl_multifit
Date: Wed, 19 Dec 2001 13:20:00 -0000 [thread overview]
Message-ID: <4DFD94A38EB3104E838576A77AEBB36E166DC7@hermes.mathcore.se> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2240 bytes --]
Hi again,
I used Matlab to compute the solution to a least squares problem
with the same sizes as you have and got the following results
> system with Athlon 1GHz, 640MB running Linux-2.4.10
> Order: (300,200) (600,400) (900,600) (1200,1000) (1500,1200)
> Octave: 0.340s 3.320s 11.580s 1m9.680s 2m1.090s
> gsl(QR): 0.390s 4.560s 22.690s 1m38.640s 5m1.580s
system Athlon 700MHz 256Mbytes running win2000
Matlab5.3: 0.1500s 1.342s 4.417s 15.873s 28.362s
(with the LAPACK patch)
If speed is what you want I should use LAPACK directly
(see www.netlib.org/clapack/ use the LAPACK routine DGELS) with a
optimized BLAS (see www.netlib.org/atlas) There has been a *lot*
of effort in writing LAPACK and BLAS routines, they are highly
optimized to use the cache in a good way (use block methods e.t.c.).
It is very easy to write for example a matrix multiplication routine,
it's really hard to get it efficient. Look at this page to see the
speedup they obtained in Matlab when they changed from LINPACK
(older linear algebra package) to LAPACK and used an optimized BLAS.
http://www.mathworks.com/company/newsletter/clevescorner/winter2000.cleve.sh
tml
Sincerely,
/Mikael Adlers
------------------------------------------------------------------
Mikael Adlers, Ph.D. email: mikael@mathcore.com
MathCore AB phone: +4613 32 85 07
Wallenbergsgata 4 fax: 21 27 01
SE-583 35 Linköping, Sweden http://www.mathcore.com
> -----Original Message-----
> From: Kai Trukenmueller [ mailto:trukenm@ag2.mechanik.tu-darmstadt.de ]
> Sent: den 18 oktober 2001 18:21
> To: gsl-discuss@sources.redhat.com
> Subject: Re: gsl_multifit
>
>
> Hi,
>
> > You could try computing the solution using the following
> > functions instead and see if you get any speed improvement.
> > gsl_linalg_QR_decomp
> > gsl_linalg_QR_lssolve
> Thanks for the tip. It's much faster now, but still slower
> than octave.
>
> Order: (300,200) (600,400) (900,600) (1200,1000)
> (1500,1200)
> Octave: 0.340s 3.320s 11.580s 1m9.680s 2m1.090s
> gsl(QR): 0.390s 4.560s 22.690s 1m38.640s 5m1.580s
> --
> :wq `Kai Trukenmueller'
>
next reply other threads:[~2001-12-19 13:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 13:20 Mikael Adlers [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-19 13:20 gsl_multifit Kai Trukenmueller
2001-12-19 13:20 ` gsl_multifit Brian Gough
2001-12-19 13:20 ` gsl_multifit Kai Trukenmueller
2001-12-19 13:20 ` gsl_multifit Brian Gough
2001-12-19 13:20 gsl_multifit Mikael Adlers
2001-12-19 13:20 ` gsl_multifit Kai Trukenmueller
2001-12-19 13:20 ` gsl_multifit Brian Gough
2001-12-19 13:20 ` gsl_multifit Henry Sobotka
2001-12-19 13:20 ` gsl_multifit Brian Gough
2001-12-19 13:20 ` gsl_multifit Dirk Eddelbuettel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DFD94A38EB3104E838576A77AEBB36E166DC7@hermes.mathcore.se \
--to=mikael@mathcore.com \
--cc=gsl-discuss@sources.redhat.com \
--cc=trukenm@ag2.mechanik.tu-darmstadt.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).