From: "M.Baris Demiray" <baris@labristeknoloji.com>
To: Chris <nanakos@wired-net.gr>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Array Empty Slots
Date: Tue, 05 Apr 2005 15:03:45 +0000 [thread overview]
Message-ID: <4252A8D1.1070100@labristeknoloji.com> (raw)
In-Reply-To: <002c01c539be$cecdcb10$0101010a@dioxide>
[-- Attachment #1: Type: text/plain, Size: 1612 bytes --]
Hi Chris,
Chris wrote:
> ..
> The well known constraints are small memory footprint
Well, then using a bitmap looks like a better solution. Since a minimal
node (a integer value and the next one's address) in a linked list takes
~64 bits but it'll take 1 bit in a bitmap.
But, you should calculate and compare the possible memory requirements
before ignoring the use of separate empty record list method. Since its
implementation will be much more easier than the former.
> and lack of
> computing power is really a concern,
I think the computer itself is the real bottleneck :-)
> but most of all is that the array is
> bigger and bigger over time, because it is and array constructed from a
> database query through a C API interface.
May be you should leave the job to DBMS by querying empty
records. I'm sure that it'll handle it more efficiently.
Also, adding a Boolean field for empty/full status and creating
an index for it will also be a good solution. But, this path ends
in off-topic.
Some benchmarking is required to tell the final word.
Regards.
> The bottleneck in the final application is this point, where the algorithm
> searches the array to find the empty slots and then fill those slots with
> data.
> Is there really sth that can 'dissapear' that bottleneck? Do u have any
> suggestions??
>
>
> 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
prev parent reply other threads:[~2005-04-05 15:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 17:05 strace write/read output Fabio Miranda Hamburger
2005-03-22 19:05 ` Eric Bambach
2005-03-22 18:16 ` Fabio Miranda Hamburger
2005-03-23 2:17 ` Eric Bambach
2005-03-23 17:34 ` Rechberger Markus
2005-04-04 14:32 ` Array Empty Slots Chris
2005-04-05 8:39 ` M.Baris Demiray
2005-04-05 9:06 ` Chris
2005-04-05 15:03 ` M.Baris Demiray [this message]
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=4252A8D1.1070100@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).