[ 
https://issues.apache.org/jira/browse/IGNITE-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15565753#comment-15565753
 ] 

Pavel Tupitsyn edited comment on IGNITE-1915 at 10/12/16 11:20 AM:
-------------------------------------------------------------------

1,2) Reverted (temp code)
3) Fixed
4) Done (local flag + get before putIfAbsent)
5,6,7) Done
8) Primary node check added instead


was (Author: ptupitsyn):
1,2) Reverted (temp code)
3) Fixed
4) This does not make sense to me. Do you mean that 
{code}if (get() == null) then putIfAbsent(){code}
is faster than plain
{code}putIfAbsent(){code}? I expect putIfAbsent to be as efficient as possible 
by itself.
5,6,7) Done
8) Which modes will be correct?

> .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)

Reply via email to