> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.syncspider.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# What are Operations (Bulk operations), and how to calculate them?

If you consider calculating Task runs and/or Bulk Operations too confusing, we’ll try to explain them as simply as possible in this help article.

**So, what are Bulk Operations?**

Bulk Operations represent the number of actions/operations sent-received/synced within a task run (importing and exporting items, changing prices on a larger scale, assigning products to a warehouse).

In SyncSpider we have a unique feature to send a large number of operations in one task run, that's why we call them **bulk operations.**

Let’s continue with the formula:

**O = EI x A**

**O - number of operations**

**EI - number of Items within the Entities (Data set e.g., Products, Contacts, Leads)**

**A - number of Attributes (Specific properties that further define an Entity, e.g., Price, Country of Origine, etc.), counted in a set of 10**

You don’t like math? Okay, let’s explain that in words.

Everything starts with **_Entities, Items,_** and **_Attributes_**.

**_Entities_** are, as the name said, entities, a sort of data. Typical entities are products, services, collections, contacts, or other sets of data. They are a type of Data that one integration can Import or Export.

![Entities are the main data you will select for your Integration. In this case, Product.](https://storage.crisp.chat/users/helpdesk/website/-/7/b/9/b/7b9bb4283bd1d000/143c2843-8164-458a-a6cc-e45b44_1lyoa0z.png)

_Entities are the main data you will select for your Integration. In this case, Product._

Every entity has a specific set of **_Attributes_**.

**Attributes** are data items within your entity. They are specific properties that further define an Entity and can vary. _Typical attributes for a product entity are price, product name, category, country of origin, contact._

![Attributes are all the “fields” you are mapping within your task. ](https://storage.crisp.chat/users/helpdesk/website/-/4/3/8/8/4388fa0c646fec00/f55bcdda-779a-4f87-82ea-105005_18qo58p.png)

_Attributes are all the “fields” you are mapping within your task._

You may also imagine **_Entities_** as a Sheet, **_Items_** as a Row in that sheet. Every row has its columns, and you can consider **_Attributes_** as the value within the Columns.

Back to the formula.

So, the number of operations will depend on the number of **_Entities’ Items_** and the set of **_Attributes_** you send.

But, there’s a catch.

**SyncSpider considers 10 attributes as 1 operation. That means**:

* If you have 10 attributes within 1 entity, it equals 1 operation.
* If you have 11 attributes within your entity, SyncSpider will consider it as 2 operations.

**_Let us put that in an example of sending products:_**

* _If you are sending 4 products (Items), and each product has 16 attributes, you’ll be consuming 8 operations._
* _If you are sending 4 products (Items), and each product has 6 attributes, you’ll be consuming 4 operations._

And there you go!

You can easily calculate how many bulk operations you have and optimize them if necessary. For example, in the first example, only cutting down Attributes by 6 for each entity (10 instead of 16) would decrease the number of operations by half (and you would have 4 operations)

**Note: This is a good thing to consider when mapping a task. You can save a lot of operations if you only map attributes you really need for that task.**

---

We hope this helped, and if you want to [find out more about Attributes and Entities](https://syncspider-support.freshdesk.com/en/support/solutions/articles/3000115865-what-is-an-entity-), you can read one more Help article we prepared for you.