You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2016/09/09 14:34:20 UTC
[jira] [Comment Edited] (IGNITE-1915) .NET: Ignite as Entity
Framework Second-Level Cache
[ https://issues.apache.org/jira/browse/IGNITE-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15477106#comment-15477106 ]
Pavel Tupitsyn edited comment on IGNITE-1915 at 9/9/16 2:33 PM:
----------------------------------------------------------------
Another option to purge old entries is an async broadcast: each node will remove old entries for a specific key:
* get current version for a key
* Iterate over cache.localEntries and purge all where version is lower
* use GridInternal annotation to execute the task in management pool and do not starve public pool
was (Author: ptupitsyn):
Another option to purge old entries is an async broadcast: each node will remove old entries for a specific key.
> .NET: Ignite as Entity Framework Second-Level Cache
> ---------------------------------------------------
>
> Key: IGNITE-1915
> URL: https://issues.apache.org/jira/browse/IGNITE-1915
> Project: Ignite
> Issue Type: Task
> Components: platforms
> Affects Versions: 1.1.4
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Labels: .net, roadmap
> Fix For: 1.8
>
>
> Entity Framework is #1 ORM for .NET
> We should provide easy solution to boost Entity Framework performance with Ignite.
> EF5 and EF6 have different 2nd level cache mechanisms (EF5 has a built-in one, EF6 requies more customization or a 3rd party lib like https://efcache.codeplex.com/). For now, let's do EF6 only.
> This should be in a separate assembly and a separate NuGet package.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)