From: "M.Baris Demiray" <baris@labristeknoloji.com>
To: Chris <nanakos@wired-net.gr>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Fw: Array Empty Slots
Date: Tue, 05 Apr 2005 16:48:55 +0000 [thread overview]
Message-ID: <4252C177.7020601@labristeknoloji.com> (raw)
In-Reply-To: <004f01c539e0$ad829180$0101010a@dioxide>
[-- Attachment #1: Type: text/plain, Size: 1962 bytes --]
Hi Chris,
Chris wrote:
> Thank you very much for your response.
> The problem maybe is in the DBMS query.I am not a DBA guru but i cant find
> until now an atomic operation (query ) that can handle this kind of
> procedural algorithm.Do you have sth to suggest?
No, the algorithm is already in the DBMS. You should only SELECT the
records WHERE their values is empty. And that's what you need, array of
empty records. Take a look at the index hint in my previous reply.
> Another problem is that in the next version of this application the C
> interface will go away and the application will be a Web based one.This is
> a
> bigger problem cause php is much slower in array searching operations.I
> have
> looked a lot of bench's for this subject and i dont see positive results.> Do you know or have sth to suggest for the web based operation?
Sorry, neither i'm a web developer, nor this is the proper place to
discuss.
> Its gone be
> much more difficult to solve this problem because the bottleneck there,
> should not concern only the computer but the language and the algorithm
> also.Please if you have sth to suggest, can you include some source code
> for
> benchmarking if its no trouble for you?
A basic benchmarking can be done with usual library functions and system
calls. For example, gettimeofday [1] system call can return milliseconds
sensitive and clock_gettime [2] function can return nanoseconds
sensitive time information. These sensitivity will be enough i think.
Write tiny array searching and database querying codes and get time
differences. These will give some idea.
Regards.
[1] man 2 gettimeofday
[2] man 3 clock_gettime
>
> Best regards,
> Chris.
--
"You have to understand, most of these people are not ready to be
unplugged. And many of them are no inert, so hopelessly dependent
on the system, that they will fight to protect it."
Morpheus
[-- Attachment #2: baris.vcf --]
[-- Type: text/x-vcard, Size: 342 bytes --]
begin:vcard
fn:M.Baris Demiray
n:Demiray;M.Baris
org:Labris Teknoloji
adr:;;Teknokent Silikon Bina No:24 ODTU;Ankara;;06531;Turkey
email;internet:baris@labristeknoloji.com
title:Yazilim Gelistirme Uzmani
tel;work:+903122101490
tel;fax:+903122101492
x-mozilla-html:FALSE
url:http://www.labristeknoloji.com
version:2.1
end:vcard
next prev parent reply other threads:[~2005-04-05 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 13:09 Fw: Array Empty Slots Chris
2005-04-05 16:48 ` M.Baris Demiray [this message]
[not found] ` <002701c539e8$093d85f0$0101010a@dioxide>
[not found] ` <4252C84F.3070600@labristeknoloji.com>
2005-04-05 14:25 ` Chris
2005-04-05 16:50 ` Luciano Moreira - igLnx
[not found] ` <32785.62.38.143.174.1112726575.squirrel@webmail.wired-net.gr>
2005-04-05 19:51 ` Luciano Moreira - igLnx
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=4252C177.7020601@labristeknoloji.com \
--to=baris@labristeknoloji.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=nanakos@wired-net.gr \
/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 NNTP newsgroup(s).