Spectra can be very memory-hungry, particularly when combining large 
numbers
of objects with Verity.  CF4.51 isn't very nice about releasing 
memory, once
it has obtained it from the system.  I have heard, however, that this 
was
vastly improved with CF5.  As I see it, you options might be to (1) 
increase
your memory (1GB is fairly common with a heavily-populated Spectra), 
or (2)
upgrade to CF5.  Of both, of course. :)

Sorry if this isn't too helpful... I'm sure others will have better
suggestions...!?

Nathan Wheat
Technical Sales Consultant
Firmware Design
Phone:  0401 148 989
Email:  [EMAIL PROTECTED]
http://www.firmware.com.au

Are you a Web Developer or Designer?
Looking for an edge? If so, check out Web Design 2001
Go to the link Below to find out more & register
<http://wd2001.firmware.com.au/ft>




-----Original Message-----
From: Stephen Collins [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 19 July 2001 4:43 PM
To: Spectra-Talk
Subject: RE: Large object sets, lots of data, Verity and memory


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aaron

We ALREADY do incremental updates automatically as well.  A script
goes and looks each hour for updated objects within the last hour and
does what you've suggested.  It works a treat as it only updates a
few objects at a time.

The script causing me problems is a weekly full rebuild of the
indexes the client has requested on the basis of their worry that
incremental index updates will ultimately make the index work at a
less than optimal level.  I don't really know whether this is valid
or not, but it's a deliverable.

Steve
========================================================
Stephen Collins, Technical Consultant - ACIS (Australia)

 Work : [EMAIL PROTECTED] Personal : [EMAIL PROTECTED]
 ICQ UIN : 56321783                       Yahoo! : trib

  "Before I got into triathlon, I was a normal person."


> -----Original Message-----
> From: Aaron Shurmer [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, 19 July 2001 4:30 PM
> To: Spectra-Talk
> Subject: RE: Large object sets, lots of data, Verity and memory
>
>
> Stephen,
> Just a side note, I hope you are locking the application var reads,
> or making sure that there are never any writes taking place after
> the  first
> application hit takes place, or this could corrupt, but anyway.
>
> Have you though of doing your verity updates incrementally, like,
>
> ************
> <cfquery name="qGetObjects"
> datasource="#Request.cfa.datasource.dsn#"> select objectid
> from objects
> where typeid = '#typeid#'
> and DATETIMELASTUPDATED > '#lastIndexUpdate#'
> </cfquery>
>
> <cfif qGetObjects.recordcount>
>       <cfset lobjectids = valuelist(qGetObjects.objectid)>
>       <cfa_typeindexkeyupdate typeID="#typeid#"
> lObjectIDs="#lobjectids#"
> dataSource="#Request.cfa.datasource.dsn#">
>       <cfa_metadataindexupdate lObjectIDs="#lobjectids#"
> datasource="#Request.cfa.datasource.dsn#">
> </cfif>
> ************
>
> This will update the verity index for every object updated since
> the  last
> time the update was run, all you have to do is store the last
> updated  time
> to file, and off you go, you may also wish to make the
> lastIndexUpdate =
> lastIndexUpdate - 1 hour or something to pick up changes that took
> place
> while the script is running...
>
> Hope that is of some use.
>
> Cheers,
Aaron.

-----BEGIN PGP SIGNATURE-----
Version: PGP Personal Privacy 6.5.8

iQA/AwUBO1X01n65o/U9+lJVEQIA5gCfe9yOiwVvHfp13snvV/CQ1GPvgYoAnido
iKO0y0i+K/NgH6EyIXuqa5b2
=EuGw
-----END PGP SIGNATURE-----
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Reply via email to