No. You are not correct. Most DBMS's compile and optimize complex queries
as a separate operation before doing data retrieval -- but even the most
complex query is actually implemented as a series of simple retrievals
(which is what the database is truly designed to do). On the other hand,
communication to and from your database -- particularly across a network --
is very likely to be a speed problem. My solution is to actually implement
your inference in the database engine. That way the database handles all of
your memory management, caching, storage, etc., etc.
----- Original Message -----
From: "YKY (Yan King Yin)" <[EMAIL PROTECTED]>
To: <agi@v2.listbox.com>
Sent: Thursday, April 17, 2008 12:51 AM
Subject: [agi] database access fast enough?
For those using database systems for AGI, I'm wondering if the data
retrieval rate would be a problem.
Typically we need to retrieve many nodes from the DB to do inference.
The nodes may be scattered around the DB. So it may require *many*
disk accesses. My impression is that most DBMS are optimized for
complex queries but not for large numbers of simple retrievals -- am I
correct about this?
YKY
-------------------------------------------
agi
Archives: http://www.listbox.com/member/archive/303/=now
RSS Feed: http://www.listbox.com/member/archive/rss/303/
Modify Your Subscription:
http://www.listbox.com/member/?&;
Powered by Listbox: http://www.listbox.com
-------------------------------------------
agi
Archives: http://www.listbox.com/member/archive/303/=now
RSS Feed: http://www.listbox.com/member/archive/rss/303/
Modify Your Subscription:
http://www.listbox.com/member/?member_id=8660244&id_secret=101455710-f059c4
Powered by Listbox: http://www.listbox.com
