This project has moved. For the latest updates, please go here.

75MB log files for 6MB data?!?

Mar 10, 2012 at 11:52 AM

Hi,

I just started using the library and im saving about 200 entries in a PersistentDictionary resulting in 6MB of data, but in the directory there are 75MB of *.log files.

Is this really necessary (which would make the library useless for me) or how can I change that behaviour?

 

regards

Mar 16, 2012 at 4:53 PM

That shouldn't happen, circular logging should keep the size down. Can you give a bit more information:

  1. What version are you using?
  2. Can you give an example of the code you are using to put stuff in the directory?
  3. Can you list the files in the directory, including all the logfiles?

thanks,

--Laurion

Mar 17, 2012 at 9:19 AM

Hi,

@1: I'm using V1.6.0.0

@2: I'm putting the following struct into the dictionary (the strings contain Base64-encoded byte[]-data):

[Serializable]
public struct ModuleInfoCacheItem
{
	public string Id;

	public string IconBig;
	public string IconSmall;
	public string Preview;

	public ModuleInfoCacheItem(string id)
	{ 
		Id = id;
		IconBig = IconSmall = Preview = null;
	}
}

@3: The folder contains the following files:

  • epc.chk - 8KB
  • epc.log - 1MB
  • epc00xx.log -> xx*66 - 1MB each
  • epcres00001.js - 1MB
  • epcres00001.js - 1MB
  • PersistentDictionary.edb - 6.1MB

 

The strange thing is, that I use the dictionary in a persitent cache implementation and use a second one to store a DateTimeOffset with the expiration time of each struct and the is only one epc.log file.

Mar 24, 2012 at 10:36 AM

The project where I have that problem is now published, so you can check my implementation:

The usage if the dictionary: http://memorylifter.codeplex.com/SourceControl/changeset/view/10375#171721

And the "data filling": http://memorylifter.codeplex.com/SourceControl/changeset/view/10375#169224 at the end of the "LoadWebContent"-method