On 04/03/17 04:05, Alan Swanson wrote:
On Fri, 2017-03-03 at 12:24 +1100, Timothy Arceri wrote:
On 03/03/17 11:53, Marek Olšák wrote:
OK.
I also wonder if 1GB isn't too conservative. Today’s games take up
a
lot of space. My installed games occupy 480 GB. I could certainly
spare 10 GB for a
On Fri, 2017-03-03 at 12:24 +1100, Timothy Arceri wrote:
> On 03/03/17 11:53, Marek Olšák wrote:
> >
> > OK.
> >
> > I also wonder if 1GB isn't too conservative. Today’s games take up
> > a
> > lot of space. My installed games occupy 480 GB. I could certainly
> > spare 10 GB for a shader cache if
On 03/03/17 00:16, Grazvydas Ignotas wrote:
On Thu, Mar 2, 2017 at 8:36 AM, Timothy Arceri wrote:
On 02/03/17 17:17, Ilia Mirkin wrote:
On Thu, Mar 2, 2017 at 1:08 AM, Timothy Arceri
wrote:
Previously we were deleting the entire cache if a user switched
between 32 and 64 bit applicatio
On 03/03/17 11:53, Marek Olšák wrote:
OK.
I also wonder if 1GB isn't too conservative. Today’s games take up a
lot of space. My installed games occupy 480 GB. I could certainly
spare 10 GB for a shader cache if it improves gaming experience. For
example, my ccache size is set to 27 GB, because 1
OK.
I also wonder if 1GB isn't too conservative. Today’s games take up a
lot of space. My installed games occupy 480 GB. I could certainly
spare 10 GB for a shader cache if it improves gaming experience. For
example, my ccache size is set to 27 GB, because 1 or 5 or 10 GB
wasn't enough for my use
On 03/03/17 07:47, Timothy Arceri wrote:
On 03/03/17 03:39, Marek Olšák wrote:
On Thu, Mar 2, 2017 at 5:36 PM, Mike Lothian wrote:
I'm guessing when the code runs the 32bit and 64bit have different build
times so invalidate the cache and create a new one
On Thu, 2 Mar 2017 at 16:25 Marek
On 03/03/17 03:39, Marek Olšák wrote:
On Thu, Mar 2, 2017 at 5:36 PM, Mike Lothian wrote:
I'm guessing when the code runs the 32bit and 64bit have different build
times so invalidate the cache and create a new one
On Thu, 2 Mar 2017 at 16:25 Marek Olšák wrote:
On Thu, Mar 2, 2017 at 3:03
On Thu, Mar 2, 2017 at 5:36 PM, Mike Lothian wrote:
> I'm guessing when the code runs the 32bit and 64bit have different build
> times so invalidate the cache and create a new one
>
> On Thu, 2 Mar 2017 at 16:25 Marek Olšák wrote:
>>
>> On Thu, Mar 2, 2017 at 3:03 PM, Mike Lothian wrote:
>> > Is
Could the solution be keeping X number of cache's and delete the oldest
ones, I guess we'd need at least 2
On Thu, 2 Mar 2017 at 16:36 Mike Lothian wrote:
> I'm guessing when the code runs the 32bit and 64bit have different build
> times so invalidate the cache and create a new one
>
> On Thu, 2
I'm guessing when the code runs the 32bit and 64bit have different build
times so invalidate the cache and create a new one
On Thu, 2 Mar 2017 at 16:25 Marek Olšák wrote:
> On Thu, Mar 2, 2017 at 3:03 PM, Mike Lothian wrote:
> > Is this because the 32bit and 64bit versions have slightly differe
On 02/03/2017 17:24, Marek Olšák wrote:
On Thu, Mar 2, 2017 at 3:03 PM, Mike Lothian wrote:
Is this because the 32bit and 64bit versions have slightly different time
stamps used in the cache directory name? I was under the impression that the
cache itself could be shared between 32bit & 64bit?
On Thu, Mar 2, 2017 at 3:03 PM, Mike Lothian wrote:
> Is this because the 32bit and 64bit versions have slightly different time
> stamps used in the cache directory name? I was under the impression that the
> cache itself could be shared between 32bit & 64bit?
>
> I guess this only matters for the
Is this because the 32bit and 64bit versions have slightly different time
stamps used in the cache directory name? I was under the impression that
the cache itself could be shared between 32bit & 64bit?
I guess this only matters for the few games that offer both a 32bit and
64bit binary, producing
On Thu, Mar 2, 2017 at 8:36 AM, Timothy Arceri wrote:
>
>
> On 02/03/17 17:17, Ilia Mirkin wrote:
>>
>> On Thu, Mar 2, 2017 at 1:08 AM, Timothy Arceri
>> wrote:
>>>
>>> Previously we were deleting the entire cache if a user switched
>>> between 32 and 64 bit applications.
>>> ---
>>> src/util/di
On 02/03/17 17:17, Ilia Mirkin wrote:
On Thu, Mar 2, 2017 at 1:08 AM, Timothy Arceri wrote:
Previously we were deleting the entire cache if a user switched
between 32 and 64 bit applications.
---
src/util/disk_cache.c | 21 +
1 file changed, 21 insertions(+)
diff --git a
On Thu, Mar 2, 2017 at 1:17 AM, Ilia Mirkin wrote:
> On Thu, Mar 2, 2017 at 1:08 AM, Timothy Arceri wrote:
>> Previously we were deleting the entire cache if a user switched
>> between 32 and 64 bit applications.
>> ---
>> src/util/disk_cache.c | 21 +
>> 1 file changed, 21 i
On Thu, Mar 2, 2017 at 1:08 AM, Timothy Arceri wrote:
> Previously we were deleting the entire cache if a user switched
> between 32 and 64 bit applications.
> ---
> src/util/disk_cache.c | 21 +
> 1 file changed, 21 insertions(+)
>
> diff --git a/src/util/disk_cache.c b/src/u
Previously we were deleting the entire cache if a user switched
between 32 and 64 bit applications.
---
src/util/disk_cache.c | 21 +
1 file changed, 21 insertions(+)
diff --git a/src/util/disk_cache.c b/src/util/disk_cache.c
index 3abdec4..1a91c69 100644
--- a/src/util/disk_c
18 matches
Mail list logo
